Hi There
So I recently picked up an A7 Lite at a Flea Market for $5 and for when I tried to set it up. It was FRP'd. So I'm wondering if there's a way to Bypass FRP on this Tablet on 13?
Samsung A22 5G FRP Reset using SP Flash Tools - Works irrespective of Android versions installed.
Samsung A22 5G FRP Reset - Works irrespective of Android version installed. Credits: Thanks to xda developer @Xyz who discovered the MTK exploit and made auth bypass possible. You can support him on github. This tutorial shall work on Any...
forum.xda-developers.com
alecxs said:
Samsung A22 5G FRP Reset using SP Flash Tools - Works irrespective of Android versions installed.
Samsung A22 5G FRP Reset - Works irrespective of Android version installed. Credits: Thanks to xda developer @Xyz who discovered the MTK exploit and made auth bypass possible. You can support him on github. This tutorial shall work on Any...
forum.xda-developers.com
Click to expand...
Click to collapse
But here it talks about a smartphone, can I follow the same guide for A7 Lite?
It's a MediaTek device right?
alecxs said:
It's a MediaTek device right?
Click to expand...
Click to collapse
I think so, the internet says it has this processor: MediaTek Helio P22T octa-core.
So I have to take it apart to bridge the port?
don't know the KCOL0 test point, but you can try without maybe first. mtkclient has included method to enter brom by crashing preloader. just try to read something off the device emmc, then you will know.
UPDATE: I got it FRP Unlocked. Now I'm trying to Root the thing, But OEM Unlocking isn;t showing up on my end
@Brent. I used a piece of Windows software called "Android Utility" to get into BRom Mode via Download Mode
try mtkclient unlocking
https://github.com/bkerler/mtkclient#unlock-bootloader
I did that and it's then giving me the dm-verity corrupted message and then when I try to flash a Magisk Patched Boot Image with the PatcheD Odin, I still get an "Only Official Binaries" message and it won't patch.
alecxs said:
try mtkclient unlocking
https://github.com/bkerler/mtkclient#unlock-bootloader
Click to expand...
Click to collapse
okay and when flashing magisk patched boot + vbmeta straight from mtkclient instead of Odin?
alecxs said:
okay and when flashing magisk patched boot + vbmeta straight from mtkclient instead of Odin?
Click to expand...
Click to collapse
I never tried that. How would I do that part?
refer to 8.
https://github.com/bkerler/mtkclient#root-the-phone-tested-with-android-9---12
Code:
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
alecxs said:
refer to 8.
https://github.com/bkerler/mtkclient#root-the-phone-tested-with-android-9---12
Code:
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Click to expand...
Click to collapse
Thanks. But now when I boot the device out of BRom Mode. I get a "SECURE CHECK FAIL : : vbmeta" error and am unable to continue any further
bootloader is unlocked?
I get the dm-verity message for when I unlock the Bootloader, Then I reboot to Download Mode to trigger BRom Mode and then when I reflash vbmeta.img.empty. I get the "Secure Check Fail : : vbmeta" message again
alecxs said:
bootloader is unlocked?
Click to expand...
Click to collapse
maybe unlocking with mtkclient does not work on samsung devices. anyway if you have vbmeta_samsung.img in stock ROM, rename it vbmeta.img, pack together with boot.img into tar file, patch the tar file with Magisk, extract the patched tar, rename it back vbmeta_samsung.img and flash from mtkclient, then try if that makes any difference.
DerpyTails said:
I get the dm-verity message for when I unlock the Bootloader, Then I reboot to Download Mode to trigger BRom Mode and then when I reflash vbmeta.img.empty. I get the "Secure Check Fail : : vbmeta" message again
Click to expand...
Click to collapse
Please use Auth Bypass first
mvikrant97 said:
Please use Auth Bypass first
Click to expand...
Click to collapse
I just tried that and still gives me the "Secure Check Fail" issue, Does it matter if I have a US A7 Lite from T-Mobile?
DerpyTails said:
I just tried that and still gives me the "Secure Check Fail" issue, Does it matter if I have a US A7 Lite from T-Mobile?
Click to expand...
Click to collapse
Can you please PM me?
Following this thread closely. I have the same device and would be very greatful for a path to oem unlock. Please update us if you figure this out. Thank you!
Related
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Looneychoons said:
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Click to expand...
Click to collapse
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
-Alf- said:
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
Click to expand...
Click to collapse
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Looneychoons said:
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Click to expand...
Click to collapse
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
-Alf- said:
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
Click to expand...
Click to collapse
Thank you bro I'll let you know how it goes. After dload do i setup the device or wipe and factory reset, also do i check for updates or just buy credits for dc unlocker to get my bootloader code?
Looneychoons said:
buy credits for dc unlocker to get my bootloader code?
Click to expand...
Click to collapse
First check if ANE-LX2 is supported, I'm not sure...
Looneychoons said:
wipe and factory reset,
Click to expand...
Click to collapse
not necessary now
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Thanks man I'll kepl you posted.
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
Looneychoons said:
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
View attachment 5372567View attachment 5372569
Click to expand...
Click to collapse
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
-Alf- said:
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
Click to expand...
Click to collapse
Really bro thank you. You're the best.
Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot
Hi, I was just wondering if it was possible to root OxygenOS 12, if you have upgraded with a locked bootloader.
Sure. Use magisk patched boot.img
Flash with mtk client, since no fastboot in oxygen os 12, as I read.
You can extract your current boot.img and patch it or look for one shared here:
Post in thread '[STOCK][DN2103][EU] Incremental update packages & Boot images' https://forum.xda-developers.com/t/...te-packages-boot-images.4385291/post-87103777
Thank you for your reply! Can you please write some instructions about how to flash the boot.img with mtkclient, have no experience with it.
Hi, tried the method you've given above, if I flash the patched boot img or bin, it says, that the boot/recovery has been destroyed, so I had to reflash the stock one. Any fixes?
AdamBarath said:
Hi, tried the method you've given above, if I flash the patched boot img or bin, it says, that the boot/recovery has been destroyed, so I had to reflash the stock one. Any fixes?
Click to expand...
Click to collapse
Please check this guide:
Nord 2 Community notes
Nord 2 Community notes. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Checked it, thanks! My bootloader is NOT unlocked, so booting into fastboot and flashing anything won't be possible. Any other ideas? I extracted the boot.img from the full OTA.zip, patched it and that also did not work sadly.
But if your bootloader is locked you can't root your smartphone. It's the first step to do but you will lose your data. Make a backup before...
Thanks for the reply, how do I unlock my bootloader with OOS 12? I heard I can not, that's why I am trying to get root access with mtkclient with a modified (patched) boot image.
Sorry. I answered too quickly and my answer concerns OS 11. For Android 12 I don't know but normally if the bootloader is locked root is not possible. But maybe Mtkclient allows it. Very interested me too by the answer and especially a very precise methodology.
Quercy said:
Sorry. I answered too quickly and my answer concerns OS 11. For Android 12 I don't know but normally if the bootloader is locked root is not possible. But maybe Mtkclient allows it. Very interested me too by the answer and especially a very precise methodology.
Click to expand...
Click to collapse
python mtk da seccfg unlock
This answer OP, too. Need to unlock the bootloader before rooting. Full instructions of using mtk client here:
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
There are reports that on OOS 12 OnePlus disabled BROM mode, so even mtk client cannot help.
Looks that works for @AdamBarath as per post #4. Hopefully the command listed here will unlock the bootloader:
# python mtk da seccfg unlock
Then patch magisk patched boot.img. Not sure if need vbmeta, too.
Thank you, I will try it, how do I get a patched vbmeta? Is it also similarly patchable like the boot.img?
AdamBarath said:
Thank you, I will try it, how do I get a patched vbmeta? Is it also similarly patchable like the boot.img?
Click to expand...
Click to collapse
When you patch the original boot.img with magisk there is a checkbox 'patch also vbmeta' or similar. I guess all magisk patched images shared here are made this way. There's a patched vbmeta shared few times on this forum. Don't have the link right now. Almost sure that not needed in this case.
The command given above was running, but as it comes to the section with 'DA_handler', I receive an error :
"DA_handler" - [LIB]: Device has is either already unlocked or algo is unknown. Aborting."
AdamBarath said:
The command given above was running, but as it comes to the section with 'DA_handler', I receive an error :
"DA_handler" - [LIB]: Device has is either already unlocked or algo is unknown. Aborting."
Click to expand...
Click to collapse
Do you follow all the steps for rooting from the link?
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
roldev said:
Not sure if need vbmeta, too.
Click to expand...
Click to collapse
Vbmeta not required.
As for the BROM mode, it is already available in Android 12.
Kollin said:
Vbmeta not required.
As for the BROM mode, it is already available in Android 12.
Click to expand...
Click to collapse
Thank you about confirming vbmeta.
The code removed BROM mode was discussed here: https://forum.xda-developers.com/t/...eu-dn2103-unbrick-guide.4366985/post-87167867
Personally will keep 11.3 for a few months more.
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
____________________________
Firmware updating (Full update) keeping the Root:
by using "oneplus local update for android 12" the root can be kept.
Install the firmware with oplocal, dont reboot, open magisk flash it on the second slot; only now you can reboot.
DON'T REBOOT after the FW installation.
The firmware can be downloaded through the app Oxygen Updater. (Full update)
---------------------------
Attachment:
Boot Patched 10T from Indian version img
OPLocal Update for Android 12 apk
Stock boot A06 CPH2415 img
Patched Boot A06 CPH2415 (Magisk 25.2) img
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
slavekve said:
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
EtherealRemnant said:
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
Click to expand...
Click to collapse
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
EtherealRemnant said:
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
Click to expand...
Click to collapse
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed. Oneplus 7 Pro does not contain vendor_boot.img file in payload.bin
slavekve said:
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed
Click to expand...
Click to collapse
Are you not listening to me? I just told you how to do it. Boot the patched image and run the direct install. Magisk installer will do what needs to be done for you. This is also the same thing the OP has done. Ignore those other instructions you found, they are incorrect and pose problems when you take OTA updates as OnePlus is moving away from full OTAs to incremental ones that will not flash to a phone with modified images.
For the record, patched dtbo and vendor_boot are needed as well but Magisk does this for you.
Ok, I will follow the instructions above when my phone arrives
any way to activate 5g & volte on non supported carriers - countries?
akaloith said:
any way to activate 5g & volte on non supported carriers - countries?
Click to expand...
Click to collapse
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
Click to expand...
Click to collapse
I have 10T Global, Indian and Chinese ROM Full Package ZIP file, I want to try Global & Chinese ROM on Indian 8/128GB Version
already unlocked bootloader, if I Flash Global or Chinese ROM will my device brick ?
As previously I was using MSM Download Tool which was free now it need authentication, so shifted to Fastboot Enhance
Will the process of flashing via payload.bin brick my device ?
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
slavekve said:
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
Click to expand...
Click to collapse
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
ryu091 said:
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
Click to expand...
Click to collapse
So that mean all 10T devices are China made and later flashed with region specific firmware's.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Hi @slavekve , Sadique this side, sorry for the confusion. Till the OnePlus 9, you only needed to flash the patched boot.img for root.
But with the OnePlus 10 series [10 Pro], flashing patched vendor_boot and vbmeta for disabling verity seems to have become an additional requirement in numerous instances.
But thanks to @Marco589 for letting us know that he has already achieved root without the vbmeta and vendor. Henceforth I have updated my post accordingly as well.
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
gonetask said:
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Click to expand...
Click to collapse
I am in greece and carrier vodafone
will i sure have 5g and volte? cause device is not supported by vodafone greece
SREEPRAJAY said:
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
Click to expand...
Click to collapse
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Marco589 said:
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Click to expand...
Click to collapse
.\ does not work. Can you please explain which tool you used? or how you managed?