Related
Hi,
I search the recovery.img of Oukitel K10.
I have make OEM Unlock, and I can get fastboot.
I have find many fake websites to hot to do this, but realy don't trust (last time I have brick my K10000 Pro).
The better way is now to "fastboot boot test.img" and see if my phone boot before flash anything.
But I dont find a recvery.img who boot my phone
I have the "fake" ROM (I search inside, and it's seem match as mine)
The other problem is SP flash tools don't want to get me my NVRAM ...
Anyone have root is K10 ? (I have a brick until my device is not root, I don't use it in stock ROM !)
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
So, what did you use to root it?
Yea can u tell us how you did it atep by step. My flashlight its not working andi cant hear a thing on Bluetooth... Need to root this.. or someone else knows how to fix it?
I actually found a step-by-step guide here:
https://www.getdroidtips.com/twrp-recovery-oukitel-k10/
But, i got stuck at downloading the image over my phone,.... i never get green light after flashing....
The phone functions normal, after... because nothing flashed i guess...
And that guide is incomplete, you need to first disable digitally signed drivers check, otherwise the preloader won't work at all...
Did anyone else try it?
What do you guys get?
Mind to share your knowledge? How you obtain your Oukitel K10 rooted cleaned?
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
sergey1369 said:
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
Click to expand...
Click to collapse
I am not able to get to bootloader how to do that? voldown and power button does nothing but restarting phone everytime.
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
sergey1369 said:
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
Click to expand...
Click to collapse
I did turn off the phone then pressed power button and volume down button at a time then kept pressing it till logo came. as soon as I release them .. Phone just get started, instead of going to bootloader
Can anyone share recovery img file? I cant find anywhere.
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
sergey1369 said:
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
Click to expand...
Click to collapse
Thanks a lot for reply .. yes it gives me recovery propmpt
Have you got K10 Recovery? Cant find anywhere. The one link given here. Takes me to other website which need to paid membership and I tried to pay but Cant pay via paypal and developer inbox is full so cant contact him too.
Oh, that's weird, it was free. Here is a copy
Anyone know how install cleaned rom?
I keep getting bootloops as soon as I try to flash Magisk. I have no trouble flashing and starting up TWRP, but after flashing I can´t reboot to system. I also get the warning from my Pc when I connect my phone that it doesn´t recognize it. It reboots fine if I don´t flash anything. Any help? I also tried the steps on page 1 (Bootloader is successfully unlocked).
SuperSu works, but fails Safety Net, that´s why I want Magisk.
k10 ROOT
Hello Friend,
I have a K10 but I have not been able to do the ROOT, can you help me ??
What is the procedure?
FukTheRegister said:
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
Click to expand...
Click to collapse
Hey there and sorry for the late response. What steps did you do so far? Is your bootloader unlocked already? Or are you at the start and this is your first try? If it is your first try, here is a step by step guide on what to do and what you will need.
What you need:
1. The SP Flash Tool and its drivers. You can find them on the Oukitel website or in the internet. Search for SP Flash Tool and download the latest. For the drivers it´s best to get them from Oukitel. Lower right side of their website and then click Latest software Rom and choose the K10.
2. The adb and fastboot drivers. Search them on the internet.
3. Your Smartphone.
4. A computer and the data cable.
5. The SuperSU 2.82 S3 files from chainfire. Again, search them on the internet.
6. The TWRP Image from this thread.
If you have everything, you do the following:
1. If you have used your phone already, safe everything you want to keep on your computer! You will have to erase your data at least once in the process!
2. Turn your phone on and go to settings.
3. Then tap on About your phone and scroll all the way down to see its build number.
4. Tap on that 7 times in a row to get the message: Congratulations you are now a developer. Go back to the settings to see a new option, the developer options.
5. Go to the developer options and tap on allow oem unlock and also tap on enable debugging options.
6. Leave the settings and connect your phone to your computer. Push the SuperSU file to your sd card (Magisk unfortunately does not seem to work and results in a bootloop at least for me).
7. On your computer, go to the folder where you saved the adb.exe and fastboot.exe. Hold shift and open a power shell or command window in there (don´t actually know the steps for a Mac or Linux computer, sry).
8. Now type adb devices and confirm the access on your phone. If your phone doesn´t show up or there is no confirmation message on your phone, type adb kill-server and then adb devices.
9. Once your phone is confirmed, you type adb reboot-bootloader.
10. Now type fastboot oem unlock and press the volume up button on your phone to confirm the bootloader unlock.
11. Your phone will now erase your data (internal storage only, your sd card will not be touched, but may need to be set up and formatted again if it was used to extend the internal storage).
12. On your computer, type fastboot reboot and set up your phone again (just the basics, because you will have to erase it again). Don´t forget to turn on the debugging mode again.
13. Open up the SP Flash Tool on your computer and choose the scatter file from the twrp image (custom recovery). Only recovery should be ticked. Hit the download all button, connect your phone to computer and turn off the phone. Now wait till there is a green hook on your computer. This means, the download has been successfull.
14. Get to recovery mode on your phone by holding the volume up and power button at the same time and choose the first option, then hit the volume down button to enter recovery mode.
15. From here, go to the settings in the upper right corner and choose your language (ignore the message of the password and hit back).
16. Now go to Wipe and format your data.
17. Hit the restart button and press Recovery. Allow it to modify the system and pull the slider.
18. Now go to Install, choose your sd card and press SuperSU. Let it run through the process. Then restart and press system. First time the boot may take a while, so be patient.
19. Set up the phone and enjoy your root.
Magisk 17.1
Magisk 17.1 install AS IS, no warranty, no testing (yet).
!!! You can lose your data or brick your phone !!!
0. Don't try default install or upgrade via MagiskManager - you'll get bootloop.
1. You can try this boot-magisk.img (AIK repacked with force encryption and dm-verity enabled).
It works for me, but I did factory reset before trying.
- boot.img comes from OUKITEL_K10_V12_20180112.rar (I'm not sure about file's source)
fastboot flash boot boot-magisk.img
2. If your phone freeze on Oukitel logo, don't touch it. Wait.
If you stop phone here, you'll lose your data.
There is no way back - it starts data encryption.
3. If it fails, try flashing stock boot back and factory reset your phone.
fastboot flash boot boot.img
That modified boot.img did the trick. What did you modify to make it work?
The forced encryption, however, is annoying. Is there a possibility to undo that?
help ... Oukitel K10
I flash firmware Oukitel K10 by SP_MDT_v3.1828 (Format and Download All). now : looked picture(red font). Phone call ok. please help me. I from Vietnam. Thankyou!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer!
1). I am not responsible for any damage caused to your device!
2). Your warranty will be void with this tutorial!
3). This is not my work!
4). This will wipe all files and data in your device!
5). Make sure to make a backup first
This is a tutorial on how to Root, Install TWRP Custom Recovery and Install Lineage OS 14.1 Custom Rom for LG SPIRIT H420/H422 ONLY
Things you need:
LG United mobile drivers: https://lg-united-mobile-driver.en.lo4d.com/
Custom Uboot.img: https://drive.google.com/file/d/0B_UKqVTCg2_xU19xeXdaLV92VDQ/view
Custom Recovery TWRP_3.0_LG_Spirit_H422_eng.zip Image: https://yadi.sk/d/NafiUEf1ocWPy
LG Stock Lollipop firmware (Choose the firmware for your device model!)
A. LG H420 lollipop firmware .kdz : https://lg-kdz-firmware.com/download-LGH420-DEU-GERMANY-V10D/12665.html
B. LG H422 lollipop firmware .kdz : https://lg-firmwares.com/downloads/downloader.php?fileid=7321&hash=b134d931d5941b0b2441dfb456f3e4f2
LG flash tool (2014) : http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip
ADB and Fastboot ZIP and Drivers: ZIP:https://www14.zippyshare.com/v/ufYG71o0/file.html - Drivers:https://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Custom ROM Lineage OS 14.1: https://drive.google.com/file/d/1kJ1kgKrcH-xhWTnPGAOLXBgP3-Qk9V9s/view
Open Gapps ZIP: https://opengapps.org/
Let's Start!
Part 1: Preperations!
1.Start by unziping the LG Flash Tool zip file in your desktop.
2.Move your downloaded LG Lollipop Firmware File in the LG Flash Tool folder. Install the LG United Mobile Driver you downloaded earlier.
3.Now go to your phone settings and perform a factory reset. Wait until your phone reboot in the setup wizard and turn it off by taking out the battery.
4.With your phone turned off take your usb cable, Connect the USB-A side of the cable to your PC. Hold down the Volume Up Button in your phone and connect the micro usb to your phone as you hold the Volume Up button, until it boot in Firmware Update mode.
5.Navigate to Device Manager in your PC. Check for LGE Mobile Usb Serial Port in the COM&LPT Ports Section as shown in the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.Right click on the LGE Mobile USB Serial Port and select Properties.Navigate to Port Settings section and click Advanced.
7.Go to the lower Left part of the window and change the COM number to COM20 and click OK.
Now Starts the Fun Part!
Part 2: Lollipop Downgrade!
A.Launch the LG Flash Tool with Administrator Permissions.
B. The Program should look like this:
C.Click the Folder icon and Select your downloaded KDZ file. Now Select the Normal Flash option. A window will appear. On the lower right select Start. An other window will appear. There Choose your Country and Language and click OK. Wait for the Flash process to complete.
D.Once it completes Setup your Phone as Usual.
E.When the setup is complete install KingRoot and root your phone.
F.When you have Root access launch the Google Playstore and install the Android Terminal Emulator. Also install the Mobileuncle MTK Tools App.
G.Now connect again your Phone to the PC.
Part 3: TWRP Custom Recovey Installation!
H.Unzip the TWRP_3.0_LG_Spirit_H422_eng.zip and uboot+Spirit+H422+v10d+patched.zip. Copy the TWRP Image and Uboot.img in your Phone's Internal Storage.
I.Launch the Mobileuncle MTK Tools and give it root access. Select 'Update Recovery', Select the TWRP.img and flash it. When the flash progress complete, it will ask you to reboot your phone. Click Cancel!!
J.Close the App and Open the Android Terminal Emulator. Type "su" and Allow Root access. Be careful with the next command. If you type it wrong it may brick your device!!!!!!!!!
K.Type : dd if=/sdcard/uboot.img of=/dev/uboot (This command will only work if you copy the uboot.img in the internal storage on your phone not in other folders!)
L.Wait until it finish copying data. Once it complete go to Settings>About Phone>Software Info and Tap the Build Number repeatedly until it say that you are a Developer. Now go back and a new menu will appear in Settings named 'Developer Options'. Click on it. A warning will appear. Click OK and scroll down until you see the option 'USB Debugging'. Enable it.
M.Connect your Phone with your Computer. In your Desktop Unzip the Androidtools.zip. Install the adb drivers. Open a Command Prompt and Type : cd (Drag and Drop the android tools folder and hit enter)
N.After that (Make sure you have you Phone Connected with USB Debugging Enabled!) Type: 'adb devices'. A device code must appear like this picture:
O.Now type: 'adb reboot recovery' .Your device should reboot in TWRP recovery mode. (If not you may have done some steps wrong. Try to flash again).
Part 4: Lineage OS 14.1 and Gapps Installation!
P.Once you boot in Recovery Mode you will be greeted with a Warning Screen. To contiune Slide to Allow Modifications. Select reboot and then system. When your device boot up, connect it to your Computer and Copy the Lineage OS.zip and Gapps.zip to the Internal Storage of your device(if your device isn't recognized by your PC go to Settings and Disable USB Debugging. Once your files are copied re-enable USB Debugging).
Q.Now repeat the previous steps(M-O) to boot in recovery. When you Boot in Recovery Mode Press Wipe<Advanced Wipe, select the boxes as shown and Slide to Wipe
Now is the Crucial Part!
R.Go back and select Install option. Navigate to the Lineage OS.zip file.Before you Flash click *add more zips* and navigate to the Gapps.zip. Now slide to flash and wait to complete. When the flash is complete reboot to system. Be patient because the first boot will last a long time.
Congrats you have installed Lineage OS 14.1 on LG SPIRIT H420!
I hope this Tutorial helped you. Coment to tell me your Opinion about this Tutorial. I'm a newbie so don't hesitate to correct me in some form.Thank's
The file has removed, plz upload again. Sorry for my english
Info?
bruno349 said:
The file has removed, plz upload again. Sorry for my english
Click to expand...
Click to collapse
Thanks for your message. Please I need more info about your requested file, phone etc.
KostasDgr said:
Thanks for your message. Please I need more info about your requested file, phone etc.
Click to expand...
Click to collapse
Is the Lineage OS 14.1 rom for the LG Spirit H422
Fixed link!
bruno349 said:
Is the Lineage OS 14.1 rom for the LG Spirit H422
Click to expand...
Click to collapse
I have just replaced the link of the lineage os with a new working from google drive.
Could you point out where that LineageOS ROM is coming from or was this created by you?
Looking for a working LineageOS version for an LG H420. (H422 should be the same hardware judging from reading through most ROM threads so far)
The ADB drivers on zippyshare are gone: https://www14.zippyshare.com/v/ufYG71o0/file.html
.
Copro said:
Could you point out where that LineageOS ROM is coming from or was this created by you?
Looking for a working LineageOS version for an LG H420. (H422 should be the same hardware judging from reading through most ROM threads so far)
Click to expand...
Click to collapse
this rom comes from 4panda which is a russian forum. This is not my work. recently the rom download link from the thread was deleted and I reuploaded the rom with google drive.
Also we working on it building our own rom. If you want you can wait and download it
Bro ,whatsapp not work , have solution? Please, update ou anything
Whatsapp stay frezee on "initializing"
KostasDgr said:
Disclaimer!
1). I am not responsible for any damage caused to your device!
2). Your warranty will be void with this tutorial!
3). This is not my work!
4). This will wipe all files and data in your device!
5). Make sure to make a backup first
This is a tutorial on how to Root, Install TWRP Custom Recovery and Install Lineage OS 14.1 Custom Rom for LG SPIRIT H420/H422 ONLY
Things you need:
LG United mobile drivers: https://lg-united-mobile-driver.en.lo4d.com/
Custom Uboot.img: https://drive.google.com/file/d/0B_UKqVTCg2_xU19xeXdaLV92VDQ/view
Custom Recovery TWRP_3.0_LG_Spirit_H422_eng.zip Image: https://yadi.sk/d/NafiUEf1ocWPy
LG Stock Lollipop firmware (Choose the firmware for your device model!)
A. LG H420 lollipop firmware .kdz : https://lg-kdz-firmware.com/download-LGH420-DEU-GERMANY-V10D/12665.html
B. LG H422 lollipop firmware .kdz : https://lg-firmwares.com/downloads/downloader.php?fileid=7321&hash=b134d931d5941b0b2441dfb456f3e4f2
LG flash tool (2014) : http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip
ADB and Fastboot ZIP and Drivers: ZIP:https://www14.zippyshare.com/v/ufYG71o0/file.html - Drivers:https://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Custom ROM Lineage OS 14.1: https://drive.google.com/file/d/1kJ1kgKrcH-xhWTnPGAOLXBgP3-Qk9V9s/view
Open Gapps ZIP: https://opengapps.org/
Let's Start!
Part 1: Preperations!
1.Start by unziping the LG Flash Tool zip file in your desktop.
2.Move your downloaded LG Lollipop Firmware File in the LG Flash Tool folder. Install the LG United Mobile Driver you downloaded earlier.
3.Now go to your phone settings and perform a factory reset. Wait until your phone reboot in the setup wizard and turn it off by taking out the battery.
4.With your phone turned off take your usb cable, Connect the USB-A side of the cable to your PC. Hold down the Volume Up Button in your phone and connect the micro usb to your phone as you hold the Volume Up button, until it boot in Firmware Update mode.
5.Navigate to Device Manager in your PC. Check for LGE Mobile Usb Serial Port in the COM&LPT Ports Section as shown in the image
6.Right click on the LGE Mobile USB Serial Port and select Properties.Navigate to Port Settings section and click Advanced.
7.Go to the lower Left part of the window and change the COM number to COM20 and click OK.
Now Starts the Fun Part!
Part 2: Lollipop Downgrade!
A.Launch the LG Flash Tool with Administrator Permissions.
B. The Program should look like this:
C.Click the Folder icon and Select your downloaded KDZ file. Now Select the Normal Flash option. A window will appear. On the lower right select Start. An other window will appear. There Choose your Country and Language and click OK. Wait for the Flash process to complete.
D.Once it completes Setup your Phone as Usual.
E.When the setup is complete install KingRoot and root your phone.
F.When you have Root access launch the Google Playstore and install the Android Terminal Emulator. Also install the Mobileuncle MTK Tools App.
G.Now connect again your Phone to the PC.
Part 3: TWRP Custom Recovey Installation!
H.Unzip the TWRP_3.0_LG_Spirit_H422_eng.zip and uboot+Spirit+H422+v10d+patched.zip. Copy the TWRP Image and Uboot.img in your Phone's Internal Storage.
I.Launch the Mobileuncle MTK Tools and give it root access. Select 'Update Recovery', Select the TWRP.img and flash it. When the flash progress complete, it will ask you to reboot your phone. Click Cancel!!
J.Close the App and Open the Android Terminal Emulator. Type "su" and Allow Root access. Be careful with the next command. If you type it wrong it may brick your device!!!!!!!!!
K.Type : dd if=/sdcard/uboot.img of=/dev/uboot (This command will only work if you copy the uboot.img in the internal storage on your phone not in other folders!)
L.Wait until it finish copying data. Once it complete go to Settings>About Phone>Software Info and Tap the Build Number repeatedly until it say that you are a Developer. Now go back and a new menu will appear in Settings named 'Developer Options'. Click on it. A warning will appear. Click OK and scroll down until you see the option 'USB Debugging'. Enable it.
M.Connect your Phone with your Computer. In your Desktop Unzip the Androidtools.zip. Install the adb drivers. Open a Command Prompt and Type : cd (Drag and Drop the android tools folder and hit enter)
N.After that (Make sure you have you Phone Connected with USB Debugging Enabled!) Type: 'adb devices'. A device code must appear like this picture:
O.Now type: 'adb reboot recovery' .Your device should reboot in TWRP recovery mode. (If not you may have done some steps wrong. Try to flash again).
Part 4: Lineage OS 14.1 and Gapps Installation!
P.Once you boot in Recovery Mode you will be greeted with a Warning Screen. To contiune Slide to Allow Modifications. Select reboot and then system. When your device boot up, connect it to your Computer and Copy the Lineage OS.zip and Gapps.zip to the Internal Storage of your device(if your device isn't recognized by your PC go to Settings and Disable USB Debugging. Once your files are copied re-enable USB Debugging).
Q.Now repeat the previous steps(M-O) to boot in recovery. When you Boot in Recovery Mode Press Wipe<Advanced Wipe, select the boxes as shown and Slide to Wipe
Now is the Crucial Part!
R.Go back and select Install option. Navigate to the Lineage OS.zip file.Before you Flash click *add more zips* and navigate to the Gapps.zip. Now slide to flash and wait to complete. When the flash is complete reboot to system. Be patient because the first boot will last a long time.
Congrats you have installed Lineage OS 14.1 on LG SPIRIT H420!
I hope this Tutorial helped you. Coment to tell me your Opinion about this Tutorial. I'm a newbie so don't hesitate to correct me in some form.Thank's
Click to expand...
Click to collapse
Hi, it seems that Custom Uboot.img: https://drive.google.com/file/d/0B_UKqVTCg2_xU19xeXdaLV92VDQ/view is no longer available to download
Hello there,
I managed to unlock the bootloader and the FRP for the Huawei P20 Lite ANE-LX1 (which was on emui 9)
Then I flashed Twrp-3.5.2_9-0.
It worked fine for a while. But when I tired "Wipe data", it got stuck with "Formating f2fs, Done" for 1hour.
So I rebooted the device with volume down + power.
When I try to get back in TWRP, it's getting stuck at the logo and there is also no access to eRecovry, it says "booting now" undefinitely.
And of course no access to the stock rom which says the same thing "booting now" undefinitely.
I also tried fastboot erase system.
I still have acces to the fastboot mode with bootloader unlock + FRP unlock.
Is there a way to unbrick the device?
Let me know if you need any additional info.
Thank you in advance.
Pi0312 said:
Then I flashed Twrp-3.5.2_9-0.
Click to expand...
Click to collapse
Pi0312 said:
But when I tired "Wipe data",
Click to expand...
Click to collapse
never do 'format data' in TWRP 3.4.0 and above running stock firmware, it may really brick your phone.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot getvar vendorcountry
and post results.
Do you have bootloader unlock code?
Thanks for the info about "wipe data"
Yes, I have the bootloader unlock code.
here are the results:
ANE-LX1 9.1.0.381 (C432E7R1P7)
vendorcountry: hw/eu
Pi0312 said:
Thanks for the info about "wipe data"
Yes, I have the bootloader unlock code.
here are the results:
ANE-LX1 9.1.0.381 (C432E7R1P7)
vendorcountry: hw/eu
Click to expand...
Click to collapse
Download and install Service ROM using dload method (instructions can be found in ReleaseDoc folder). This process will erase all your data and lock the BL again.
P.S.: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
First flash stock recovery with fastboot https://mega.nz/file/M0FHlYhb#4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
command:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
Thanks.
I went to the link for download the Service ROM but...
Am I missing something or the .rar file is locked with a password and one must pay for it?
Pi0312 said:
Thanks.
I went to the link for download the Service ROM but...
Am I missing something or the .rar file is locked with a password and one must pay for it?
Click to expand...
Click to collapse
No , sorry, try another links
https://androidhost.ru/1O2r
https://androidhost.ru/Y0n
Those links are for nova 3e, does it work also for ANE-LX1?
Pi0312 said:
Those links are for nova 3e, does it work also for ANE-LX1?
Click to expand...
Click to collapse
I'm not an idiot bro ....
sorry, that's not what I meant.
I'm new to this kind of things.
thank you again.
I'll try it tomorrow and report back.
Cheers
I'm in the exact same soup (and additionally flashed the phenix kernel). How exactly does one do the dload method without dialpad?
I tried:
flash twrp, got stuck on the twrp logo where ADB works, so pushed UPDATE.APP to /sdcard/dload/UPDATE.APP and tried booting while holding both volume keys and power. No luck, boots back to TWRP and stuck on logo.
Flashed stock recovery over recovery_ramdisk and tried again. No luck and stuck on "Your device is booting now..."
both of the above but with an external SD card and instead of /dload/UPDATE.APP I just copied the whole dload directory from the stock service ROM
Nothing seems to work and now I would kindly ask for help - what should I do?
MrPipa said:
How exactly does one do the dload method without dialpad?
Click to expand...
Click to collapse
-Alf- said:
instructions can be found in ReleaseDoc folder
Click to expand...
Click to collapse
Btw, what is your build number?
Try flashing a treble system image.
Release AOSP 11.0 v312 · phhusson/treble_experimentations
VoLTE on Mediatek R vendors Under-display fingerprint comeback. Partial support on OnePlus Nord2. Double-tap to wake on OnePlus Nord2 Fix fingerprint support on some OPPO/OP devices Fix securize wh...
github.com
Click assets then select the 'arm64 vanilla' build.
Extract the .xz file once and rename it system.img.
Put it into the folder that contains fastboot .
Then download this vbmeta.img and put it into the fastboot folder.
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Then execute, in fastboot:
fastboot -w
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot reboot
Got it!
I found an old message by @-Alf- where he suggested to use Huawei Update Extractor to extract system, kernel and recovery_ramdisk images from the stock service ROM and flash them manually with fastboot. This works! Or at least the stock rom and erecovery seems to boot fine.
Thank you both @-Alf- and @LR7875 ! These forums can be confusing, I'm used to Nexus 6P where there is plenty ROMs available and no issues with TWRP etc. I will now go for my second attempt to get LOS 18 to work (with magisk )
Btw the build number is ANE-LX1 9.1.0.381(C432E7R1P7) (hw/eu edition, same as OP)
Oright, I'm back in the game.
Thank you -Alf-, LR7875 and MrPipa
I too didn't manage to make the dload method work.
So I also followed Alf's suggestion to use Huawei Update Extractor.
Here is a recap for other noobs like me:
My device is:
Huawei P20 lite
Build: ANE-LX1 9.1.0.381 (C432E7R1P7)
vendorcountry: hw/eu
1. Download huawei update extractor here:
http://forum.xda-developers.com/attachment.php?attachmentid=3966156
(from this thread: https://forum.xda-developers.com/t/...updated-v0-9-9-5-open-source-library.2433454/)
2. Download Stock ROM from here: https://androidhost.ru/1O2r
(Thanks to -Alf-)
3. In windows, unzip HuaweiUpdateExtractor_0.9.9.5.zip
4. Unzip "Huawei P20 Lite ( Nova 3e )... .zip"
5. Unzip the update_sd.zip file contained in the folder path /Huawei P20 Lite ( Nova 3e ).../Software/dload/update_sd
5. Launch HuaweiUpdateExtractor.exe
6. Go in the tab settings and uncheck all boxes
7. Back to the first tab, leave the drop down field to "unknown ..."
8. Click on the 3 dots on the right side and select the file UPDATE.APP in the newly unzipped folder update_sd
9. HuaweiUpdateExtractor will show all the .img files contained in the UPDATE.APP file
10. Extract all to a folder (i.e. update-imgs) with right click on any img file and select extract all
11. Put the device in fastboot mode and start flashing .img files (see below)
(from this thread: https://forum.xda-developers.com/t/huawei-p20-lite-bricked.3798842/)
Plug in usb cable into the pc and the device, boot the device into fastboot by pressing and holding Volume Down and power buttons, hold it until it boot into fastboot
Android icon with 2 red lines under it: bootloader unlock and FRP unlock
Then open a terminal or command line in the folder containing all the images i.e. update-imgs
and use these commands:
Code:
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
I'm not sure if they are all necessary but I tried a few of them (system, recovery_ramdis, ramdisk)
and it didn't seem to work.
Only after doing the rest of them, it worked.
Meaning the device could boot into stock rom.
12. Reboot the device after the last command with:
Code:
fastboot reboot
Now back to normal.
After that I got LineageOS 16 on the device with these steps:
1. Download a TWRP, I used this one: https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
(Thanks to -Alf-, from this thread: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/)
2. Downlaod LineageOS 16 from here: https://lineageosroms.com/anne/
3. Copy the LineageOS 16 image to device's SD card.
4. Connect the device to a pc via USB cable, put the device in fastboot mode (Volume DOWN + Power buttons until the android icon appears)
then use this command line from the folder containing the TWRP image file (i.e. TWRP-oreo-smart.img):
Code:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
and reboot with:
Code:
fastboot reboot
5. To get into TWRP, unplug the USB cable and go into recovery mode by pressing and holding Volume UP + Power buttons until Huawei logo appears.
6. In TWRP:
(Again thanks -Alf-, from this thread: https://forum.xda-developers.com/t/rom-official-anne-9-lineageos-16-0.4151163/page-3#post-83601729)
6.a: go to Wipe > Format data, go back to TWRP's main menu
6.b: Wipe > Advanced Wipe > Wipe Dalvik, Cache, Data, System, Internal storage > Swipe to wipe and go back to the TWRP's main menu
6.c: Install > navigate to LineageOS 16's .img file and swipe to install LineageOS
6.d: Back to TWRP's main menu, select Reboot > Reboot recovery > perform factory reset
That part didn't work for me, it kept booting into TWRP.
So I had to get into eRecovery from TWRP, I unplugged the USB cable.
And then pressed Volume UP + Power buttons until the phone rebooted and the Huawei logo appeared.
At the Huawei logo, I released the buttons and the device booted into eRecovery.
Then I could do a factory reset by following the onscreen instructions.
Done, the device reboots and after the Huawei logo appears the LineageOS animation.
Enjoy and again thank you -Alf-, LR7875 and MrPipa
Edit: Added flashing CUST.img as per -Alf- suggestion
Edit: Added remove the USB cable to boot into eRecovery
Pi0312 said:
Done
Click to expand...
Click to collapse
Super, congrats!
P.S.: if I may add something - often it is important to flash CUST.img partition.
Pi0312 said:
6.d: Back to TWRP's main menu, select Reboot > Reboot recovery > perform factory reset
That part didn't work for me, so I had to get into eRecovery from outside TWRP by pressing Volume UP + Power buttons until eRecovery appeared
then I could do a factory reset by following the onscreen instructions.
Click to expand...
Click to collapse
Hello guys, I tried to follow these steps since i also 'bricked' my p20 lite and it worked pretty fine up until the quoted point. When I tap the factory reset the phone instantly shuts of and reboots into twrp. Any idea what could cause this?
My device is:
Huawei P20 lite
Build: ANE-LX1 9.1.0.132(C432E7R1P7)
vendorcountry: hw/eu
Since I have this build I flashed the kernel, system, recovery_ramdisk etc. with .132 build .zip, (rest of the steps were exactly the same), should I have used the .zip @-Alf- provided?
Hello LIFATRON3000,
I've tried a few build as well and they worked fine. So my guess is that the issue might not be the build.
I find that when the phone is connected to a usb cable, it keeps booting into twrp when I try to get into eRecovery.
So when in trwp, unplug the usb cable and then press Volume UP + Power button.
It should reboot the phone then you'll see the Huawei logo again. Which is when you should release the buttons.
A new screen appears after Huawei that says a few things with a yellow URL and "booting now..." in white, instead of the regular similar screen but with 3 yellow options like: press up for 3 sec or power to boot or if you do nothing it will boot by itself.
And it's after that, that eRecovery is hidden.
Have you tried that already? Unpluging the USB cable and tried to Volume UP + power button?
In Huawei devices there are two Recovery , Recovery and eRecovery, each has different functions.
How to enter Recovery on EMUI 9.1: you need to turn off the phone (unlike EMUI 8) and press and hold Power + Vol Up.
If your Recovery is patched by Magisk, use this Guide
How to enter eRecovery -
1. Locked phone -on E 9.1 - turn off, connect your phone to charger or PC, then press and hold Power +
Vol Up.
2.Unlocked phone - restart your phone, when the yellow warning appears on the screen, press and hold Vol Up for 3 sec. If you have TWRP installed instead of eRecovery, you can use this to enter TWRP.
Recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eRecovery:
Pi0312 said:
And it's after that, that eRecovery is hidden.
Click to expand...
Click to collapse
????
Thank you @-Alf-
It's good to know. I didn't know that there were 2 of them.
I thought there was only eRecovery. So far I only saw the second screen shot but not the first one.
Regarding the "And it's after that, that eRecovery is hidden."
What I mean is when the phone is unplugged and either turned off or inside of TWRP, if I press Volume UP + power button, I get this screen:
and it's ONLY after that screen that I get into eRecovery.
If I get this screen:
and press Volume UP for 3 seconds as indicated in the yellow text, I don't get in eRecovery. Instead I get back inside of TWRP.
Not sure if it's how it's supposed to be but that's what I got so far.
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research yourself before asking or use anything on this thread.
* I do not offer private assistance via Telegram or any other social outside XDA.
*/
Click to expand...
Click to collapse
This project is no longer actively mantained, help yourself in the comments! - OP switched to a custom ROM - AndroidFileHost is no longer available for uploads (downloads are still available)
Click to expand...
Click to collapse
OxygenOS 11.3 EU Full Stock Firmwares for the OnePlus Nord 2 DN2103
A.20
Specifics:
This rom will not overwrite your userdata or metadata partition.
This rom will not overwrite your IMEI, sensors calibration data, or bootloader unlock status.
Since these partitions are not included: seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
These partitions are not included since are present in the super partition: my_*, odm, product, system, vendor.
The vbmeta partition is not stock.
The vbmeta partition is stock. A vbmeta_patched partition for root users can be found attached to this thread.
Requirements:
ADB & Fastboot drivers + MTK VCOM drivers
PartitionsBackupper
Python
Mtkclient + UsbDk
Instructions:
.img and .bin files are the same. Just rename them as you need.
If you are on Android 11: Rollback guide from C.01/C.05 to Android 10
Spoiler: How to install and use Mtkclient (Windows)
Download and, install Python, extract Mtkclient, and install UsbDk.
Open a terminal (cmd) inside the extracted Mtkclient folder, and type the command pip3 install -r requirements.txt
After the installation has completed, type the command python mtk_gui to start Mtkclient GUI.
Reboot your phone in BROM mode:
Turn off your phone.
Connect the phone via usb to the pc, and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
The screen of the phone should remain completely black and Mtkclient should find your phone and connect to it, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
If the phone won't connect properly, check that's being correctly detected in device manager:
Open Device manager.
While the phone is connected in BROM mode to the pc, search for "MediaTek USB Port" under "Ports (COM and LPT)".
Right click on it -> Choose "Update driver" -> "Browse my computer for driver software" -> "Let me pick from a list of available drivers on my computer" -> and change it to "USB serial device".
Sometimes it likes to revert itself back to "MediaTek USB Port", so leave Device manager open to keep an eye on it.
If the phone keeps rebooting itself out of BROM mode, try to be fast when changing the settings inside Device manager. Keep trying until you see that "USB serial device" has stick.
If Mtkclient freezes on "waiting for preloader VCOM", or the phone keeps rebooting itself out of BROM mode, keep rebooting the phone into BROM mode without letting go of the buttons, without disconnecting it from the pc, and without closing Mtkclient. And release all the buttons just when the phone has been detected. (It could need 2 to 3 reboots. If more, disconnect the cable and retry).
You can now use Mtkclient GUI. (see the guides below)
After you're done flashing, you can exit BROM mode by press and hold Vol+ and Power.
Spoiler: OLD METHOD: ReLive DVD iso (Linux)
Download and install the Re LiveDVD iso of mtkclient and flash it on a pendrive with Rufus.
Create two new folders named "img" and "img_bak" in the pendrive you just flashed with Rufus, and paste inside /img all the files and images you will need.
Start the mtkclient live usb. The login credentials are "user" for both name and password.
Note! the keyboard is set to german by default in the liveusb. To change it, as soon as you boot up in the desktop, click on the "DE" blue text up on the right.
Copy the whole /img and /img_bak directories into the /opt/mtkclient directory.
Disconnect the phone from the pc, and start the MTK script on the desktop of the live usb.
Write the desired command (see below) and press Enter.
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
Connect the phone via usb to the pc, and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
The screen of the phone should remain completely black and Mtkclient should find your phone and connect to it, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
It is necessary to disconnect the phone, close and reopen the MTK script on the desktop, and reconnect the phone in BROM mode, every time you want to run another command.
To backup any partitions on your phone, use the command python mtk r partition_name_1,partition_name_2,partition_name_3,... img_bak/partition_name_1.img,img_bak/partition_name_2.img,img_bak/partition_name_3.img,.... Example: python mtk r boot,vbmeta,super img_bak/boot.img,img_bak/vbmeta.img,img_bak/super.img. You'll find all your backups inside the /opt/mtkclient/img_bak folder (copy them back to your pendrive to not loose them).
To write all the partitions present in the /img directory to your phone, use the command python mtk wl img. Be sure that the file names have the same name of the partition they're meant to write!Example: The file named "boot.img" <---> Will write the "boot" partition.
Use the command python mtk r preloader img_bak/preloaderdump_backup.bin --parttype=lu1 to backup your preloader partition. You'll find your backup inside the /opt/mtkclient/img_bak folder (copy it back to your pendrive to not loose it).
Use the command python mtk w preloader img/preloaderdump_stock.bin --parttype=lu1 to flash the preloader partition.
↓
Spoiler: Flash Stock firmware with UNLOCKED bootloader
If your phone is still not completely fcked up, and even if it is, do a full backup with PartitionsBackupper first + a TWRP backup + Internal storage backup. (better safe than RMA it)
Download the stock firmware .zip, and the latest version of PartitionsBackupper.
Extract both of them in the same directory where adb.exe & fastboot.exe are located (usually the "platform-tools" folder).
Run PartitionsBackupper, choosing the restore option, to flash all partitions with fastboot.
Reboot into the stock recovery and do a full data format before going back messing around. It usually wipes better than TWRP.
Spoiler: For LOCKED bootloader
Follow this guide only if the command fastboot flashing unlock does not work.
Download and extract the attached seccfg.img unlocked partition.
Download and extract the boot.img, recovery.img, and vbmeta.img from the stock firmware .zip file.
Put all 4 images in a new empty folder, and do not rename the files.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Select the seccfg, boot, recovery, and vbmeta partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
You should now have an unlocked bootloader
Spoiler: Fix corrupted fastboot / preloader partition
This procedure has been successfully tested by an external user.
This guide is useful if your device is not getting recognized via fastboot.
Download and extract the attached preloaderdump_stock.bin image.
Download and extract the boot, recovery, vbmeta, and super images from stock firmware .zip file.
Put the 4 images extracted from the stock firmware, in a new empty folder, and do not rename the files. Do not put the preloader image in this folder.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Select the boot, recovery, vbmeta and super partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
In the fourth tab "Flash Tools": Choose "Read preloader" to backup it up. Save it in a different folder from the one created before.
Still in the fourth tab "Flash Tools": Choose "Write preloader" and flash the downloaded preloaderdump_stock.bin image.
Last, in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
You should now have a working fastboot connnection
Spoiler: Flash Stock firmware via Mtkclient
This procedure has been successfully tested by an external user.
This guide is useful as a last resort. If you are not able to restore the stock rom in any other way.
Download the stock firmware and extract the folder inside the .zip file.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Choose "Select all partitions" and click "Read" to backup them up. Save them in a different folder from the one with the stock firmware.
Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the folder with the stock firmware. It should automatically place all the images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, try flashing the preloader and seccfg partitions following the guides above, and then repeat this procedure a second time.
Your device should hopefully boot now
Spoiler: My phone went into a bootloop after root!
Yeah.. Looks like OxygenOS doesn't really like to be rooted. Your phone will occasionally go into a bootloop without any notice or known reason (so far).The cause of this behavior is still unknown to me, if you are able to find any explanation or better solution please post it here!The only solution I know so far, is to just format your phone back to stock, and then restore your userdata partition:
Make a backup of your Internal storage, recovery, boot, vbmeta, and userdata partitions. Both with PartitionBackupper or Mtkclient, what's more handy for you.
Flash the stock firmware on the phone.
Format data with the stock recovery.
Restore your previously backupped partitions and storage.
When booting to system for the first time, it's possible your interface / GUI will be malfunctioning. Just reboot one more time to fix this.
Finally, go into the setting and reset your password / sequence / PIN.
Thanks to Zombnombs, TheWing, SeBright, Giovix92 for the help!
DOWNLOAD
AndroidFileHost
Can we flash this rom On locked bootloader also can we use this for Indian DN2101
pankspoo said:
Can we flash this rom On locked bootloader also can we use this for Indian DN2101
Click to expand...
Click to collapse
Right, always forgot about the bootloader. Yup that needs to be unlocked.
About the Indian model, I dunno really. I heard you guys have the A.13 update instead of the A.12 so, I wouldn't risk it. Many system partitions could still be the same for both models though.
With the tool included you can extract a stock rom of your phone anyway, if you, revert it back to stock first obv.
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock (except vbmeta..) Firmware for the OnePlus Nord 2
Extracted with PartitionsBackupper (included in the .zip)
Requirements:
ADB & Fastboot + Google & MTK drivers
Unlocked bootloader
Instructions:
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder)
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
DOWNLOAD
Gdrive
Click to expand...
Click to collapse
PASSWORD ???
muppetz said:
PASSWORD ???
Click to expand...
Click to collapse
There's no password.
Raygen said:
There's no password.
Click to expand...
Click to collapse
What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?
muppetz said:
What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?
Click to expand...
Click to collapse
I've reuploaded the .zip, please try again
Now we talking ... It's fine now , thank you!!!
this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((
Way to go, Raygen! Thank you very much!
IgorSamsonov said:
this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((
Click to expand...
Click to collapse
If the erased partitions include the persist partition, then I guess your only way is RMA.
The persist partition contains calibration data unique to your device only. It's not recoverable unless you've made a backup
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)
Specifics:
Vbmeta is not stock
Fastboot is already unlocked
Requirements:
ADB & Fastboot + Google & MTK drivers
Instructions:
For unlocked bootloader:
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
For locked bootloader:
Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
Extract just the seccfg.img partition from the zip.
Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
The script should find your phone and start the backup. Release the buttons.
Now, disconnect the phone, and close and reopen mtkclient.
Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
You should now have an unlocked bootloader!
DOWNLOAD
Gdrive
Click to expand...
Click to collapse
Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)
Specifics:
Vbmeta is not stock
Fastboot is already unlocked
Requirements:
ADB & Fastboot + Google & MTK drivers
Instructions:
For unlocked bootloader:
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
For locked bootloader:
Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
Extract just the seccfg.img partition from the zip.
Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
The script should find your phone and start the backup. Release the buttons.
Now, disconnect the phone, and close and reopen mtkclient.
Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
You should now have an unlocked bootloader!
DOWNLOAD
Gdrive
Click to expand...
Click to collapse
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
martinwildi said:
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
View attachment 5470935
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
Click to expand...
Click to collapse
Yes try that unlocking bootloader and let me know can u give me that scccf. Img file as u downloaded whole firmware
martinwildi said:
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
View attachment 5470935
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
Click to expand...
Click to collapse
That's odd, the rom is already unlocked by itself. I'll see if any others encounter the same issue.
The locked bootloader method should revert it back to unlocked.
pankspoo said:
Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?
Click to expand...
Click to collapse
The seccfg has been added to download as a separate file in the instructions
can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.
kkdamion said:
can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.
Click to expand...
Click to collapse
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
HI, again
I have had prbs with A.12 update - apps force close, sometimes OS doesn't accept my screen lock psw (numbers), sometimes stuck on boot, but I have been able to recover with force reboot. But now I am stuck on boot. Stuck where we have red dot and 2 white dots, it boots few times itself after waiting long time and then it boots to recovery (twrp).
Does your A.12 wipe/destroy user data? If it does perhaps I do factory reset and start from scrats. Or does anyone have idea how I can recover?
I tried to flash ota.zip (I have it stored) First I flashed A.11 boot.ini and then I tried to flash ota.zip but it end up with error 1. And before that there was message that system has been opened as R/W xx times. Last 29.11, unable to use metadata to correct errors. system partition fails to recover. (flashing done with TWRP).
Thank you
Raygen said:
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
Click to expand...
Click to collapse
I didn't understood means u have used iso file and flashed it in Penddrive then how to use it on windows (I think it's for Ubuntu OS)
Also seffc image is from A12 I am. Using A13 can i use thats
the livedvd, you used it how?
Raygen said:
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
Click to expand...
Click to collapse
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Edit: thanks for the answers, when I buy this phone an root it I can let you know how it went.
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
there is no problem to root xiaomi device,because it can unlock BL
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
Hello , You can unlock bootloader then root your device easily with magisk , xiaomi devices are root friendly if you need any help lemme know i will do as much as i can
I would love a step-by-step, hold my hand type of tutorial. If some of you have spare time to do something good for the less capable brothers here, it will be great.
Yeah step by step Link would bei very helpful
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "fastboot devices" your phone should appear
Method 1 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 booting in TWRP (not recommended on this device, may cause bootloop)
pros: original recovery wont be replaced
cons: loads temporary recovery, once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
GoldenWarriorM said:
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "adb devices" your phone should appear
Method 1 booting in TWRP
pros: original recovery wont be replaced
cons: loads temp recovery once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery)
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Click to expand...
Click to collapse
Just confirming: in the TWRP page, the 12T Pro is not listed as a compatible device (https://twrp.me/Devices/Xiaomi/).
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Just did as instructed and it works. Only bummer is that twrp is in Chinese. I did google a youtube video and followed instructions to change language. So far all good.
Do OTA updates still work after rooting? Or what is the process to upgrading once rooted?
GoldenWarriorM said:
7) type "adb devices" your phone should appear
Click to expand...
Click to collapse
You mean "fastboot devices", as it is already in fastboot
booting to recovery ended in error for me " FAILED (Status read failed (Too many links))" which led to bootloop.
I reflashed original ROM and I will try flashing.
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
HValenti said:
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
Click to expand...
Click to collapse
I didn't tried to boot without installing, I think there is a problem with A/B slots. On devices without B slot booting in TWRP should work as intended.
JF_Derzi said:
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Click to expand...
Click to collapse
Provided version works on my device (Mi 12T Pro, Global ROM). Hardbrick is impossible if flashing TWRP in recovery partition.
I didn't found compatible Orangefox recovery
There are 3 versions of TWRP:
BOOT:
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
REC:
Update with existing TWRP.
gold
CMD
fastboot flash recovery_ab twrp.img***
powershell
./fastboot flash recovery_ab twrp.img***
BOOT REC:
Both methods
On this thread the proposed version is REC.
***Remove lock screen security and reboot to decrypt data then install TWRP.
Reboot with the buttons combination and not with a fastboot command
Update REC
twrp-3.7.0_12-v6.5_A12-diting-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Spoiler: Change languages
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then reboot TWRP
No need TWRP for Rooting
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Xiaomi 12T Pro
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
Pass SafetyNet without Magisk Hide Props Config and
How to Hide Root from Apps via Magisk DenyList [Android 13]
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Try island app on Google play
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
NOSS8 said:
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
Click to expand...
Click to collapse
Yes I have done all of this. Links have been fixed.
tavocabe said:
Try island app on Google play
Click to expand...
Click to collapse
I don't think I can isolate Google Pay/Wallet, but I will try it.