Database Users

CWM for Nokia X2.

Hello! And, yup, it is finally done. We have custom recovery.
You can say Thanks to GRIP95 and ruslan_3_.
Installing via fastboot
Fastboot -i 0x0421 flash recovery "Recovery name.img"

Altivex said:
Hello! And, yup, it is finally done. We have custom recovery.
You can say Thanks to GRIP95 and ruslan_3_.
Installing via fastboot
Fastboot -i 0x0421 flash recovery "Recovery name.img"
Click to expand...
Click to collapse
have u tested on ur device ???

Yes. It`s working. Dudes made a wonderful job!

Altivex said:
Yes. It`s working. Dudes made a wonderful job!
Click to expand...
Click to collapse
when i try to install via fastboot ,,, it says < waiting for device > ,, i installed X2 drivers,,, whats wrong ? :/

Here are all answers. I think problem in ini file.

Altivex said:
Hello! And, yup, it is finally done. We have custom recovery.
You can say Thanks to GRIP95 and ruslan_3_.
Installing via fastboot
Fastboot -i 0x0421 flash recovery "Recovery name.img"
Click to expand...
Click to collapse
From where did you get this? Also, add some screenshots.

From where did you get this?
Click to expand...
Click to collapse
From 4pda.ru)
And , i cant promise this, but maybe, only maybe, today evening we`ll get custom kernel.

Altivex said:
Here are all answers. I think problem in ini file.
Click to expand...
Click to collapse
i installed Nokia x drivers from http://tools.nokia.com/nokia-x/repository/nokia_x_usb_driver.zip
i dont get any ini file :/ check this pic
{
"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"
}

i dont get any ini file :/ check this pic
Click to expand...
Click to collapse
Then create it =)
Paste this:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
and vendor code from dev instruction.

Altivex said:
Then create it =)
Paste this:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
and vendor code from dev instruction.
Click to expand...
Click to collapse
still having waiting for device issue

Can I install it directly by X2.
Which application can do it
Sent from my NokiaX2DS using XDA Free mobile app

Finally i installed CWM on my device ,,, it works like a charm
here is screenshot :-

it not work for me
i can flash this but when i go to recovery it blank, just "NOKIA" @@
please check recovery file
and can u post the stock file for me to check flashboot
thank u

Download this :-
https://www.dropbox.com/s/47jswar03sk1mei/nokia-x2-recovery.zip
who has problem with fastboot,,,
make sure u have installed adb drivers properly than run start.bat
than press 2 button,,, it will install cwm

Stackin said:
Download this :-
https://www.dropbox.com/s/47jswar03sk1mei/nokia-x2-recovery.zip
who has problem with fastboot,,,
make sure u have installed adb drivers properly than run start.bat
than press 2 button,,, it will install cwm
Click to expand...
Click to collapse
this method work for me. So i believe that it will work for all of us
good luck guys ^^

help
Stackin said:
Download this :-
who has problem with fastboot,,,
make sure u have installed adb drivers properly than run start.bat
than press 2 button,,, it will install cwm
Click to expand...
Click to collapse
start.bat file you can transfer it to english language ? :good:

help
finished... but I can't boot recovery ( philz )
help...

Try to unlock bootloader before flashing recovery.
fastboot -i 0x0241 oem unlock
then flash recovery.

Altivex said:
Try to unlock bootloader before flashing recovery.
fastboot -i 0x0241 oem unlock
then flash recovery.
Click to expand...
Click to collapse
GRIP95 and ruslan_3_ these russian developers are interested to make custom rom or kernel for Nokia X2 ???
they can make good rom but i dont know they have time or not to make rom

I followed the instructions to flash the CWM and fastboot reported success.
However when I reset the phone to enter recovery, all I get is the NOKIA logo.
When I try to reset the phone to enter bootloader mode, fastboot on my PC no longer recognizes it.
So now what can I do?
Stackin said:
Download this :-
https://www.dropbox.com/s/47jswar03sk1mei/nokia-x2-recovery.zip
who has problem with fastboot,,,
make sure u have installed adb drivers properly than run start.bat
than press 2 button,,, it will install cwm
Click to expand...
Click to collapse
Link doesn't work, the file has been removed.

The Absolute way to " Re-lock " The Bootloader

good morning everybody ..
after a long tired journey with staying awake till the morning I finally Figured out a way to Re-lock your Bootloader
Yes People it works in every HUAWEI MT7 Brands . :laugh:
First Of all you should Have these Requirement :
1- Your appreciated software Updated or using currently " Depends on your Brand " TL-09 or TL-10 ... etc. "
2- HuaweiUpdateExtractor and you can download it from here : http://filaty.com/Exe " Arabic website "
3- an ADB Tool you can get it from here : http://forum.xda-developers.com/mate-7/general/huawei-ascent-mate-7-unlock-recovery-t2941525
Now ,,,
1- Extract the software by using HuaweiUpdateExtractor " Easy to Use "
open it and select your UPDATE.APP and select these Three items with right click you will find " Extract "
- recovery.img
- boot.img
-system.img
you should Extract in the same ADB Folder . it will look like this
{
"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 :
>Connect the device to computer
>Setting – About phone – Build number click it for 3-5 times
>Setting – Develop options – USB debugging enabled
>Disconnect the device – Connect the device to computer authorize the Developer Mode
>WIN+R – CMD – D: – CD MT7 – adb devices (show something like Y9KF0923F898343 device)
>adb reboot-bootloader
>fastboot devices
Click to expand...
Click to collapse
2- Now do these Steps as its mentioned one by one :
fastboot flash recovery recovery.img
Then Press Enter
fastboot flash boot boot.img
Then Press Enter
fastboot flash system system.img
* the system.img will take a while so don't Be afraid :fingers-crossed:
* After each command it will say " OK "
3- use this relocking command " Fastboot oem relock XXXXXXXXXXXXX "
X= your Unlock Number.
TDAAAAAAAAAAAAAAAAAAAA :laugh:
Congrats. your Bootloader Is relocked :good:
waiting for your comments Guys

BTW ..
I was able to root again and restore back the original recovery and relock the boot loader

got error root type is risk

danger2u said:
got error root type is risk
Click to expand...
Click to collapse
U did something wrong then retry and do it by order u wint get it any error

MADOLOGY said:
U did something wrong then retry and do it by order u wint get it any error
Click to expand...
Click to collapse
so the deal is this way
flash the original firmware and recovery
boot the phone
then go back to bootloader
give this comand: fastboot oem relock 1122************
phone relocked
i relocked my MATE 7

Can you give screen after relock boot loader. What it's write on screen Lock or Relock???

danger2u said:
got error root type is risk
Click to expand...
Click to collapse
danger2u said:
so the deal is this way
flash the original firmware and recovery
boot the phone
then go back to bootloader
give this comand: fastboot oem relock 1122************
phone relocked
i relocked my MATE 7
Click to expand...
Click to collapse
Yep step by step and it will be relocked as i mentioned
chudy_85 said:
Can you give screen after relock boot loader. What it's write on screen Lock or Relock???
Click to expand...
Click to collapse
It will says relocked

I read somewhere even after relocking bootloader you can tell it's been unlocked because the writing changes a different colour which indicates it has been unlocked. Because I was planning unlocking then relocking it if anything went wrong with it in the future so I can send it back to Huawei to get it fixed.
Can someone confirm this that when relocked there are no signs of it being unlocked

MADOLOGY said:
good morning everybody ..
after a long tired journey with staying awake till the morning I finally Figured out a way to Re-lock your Bootloader
Yes People it works in every HUAWEI MT7 Brands . :laugh:
First Of all you should Have these Requirement :
1- Your appreciated software Updated or using currently " Depends on your Brand " TL-09 or TL-10 ... etc. "
2- HuaweiUpdateExtractor and you can download it from here : http://filaty.com/Exe " Arabic website "
3- an ADB Tool you can get it from here : http://forum.xda-developers.com/mate-7/general/huawei-ascent-mate-7-unlock-recovery-t2941525
Now ,,,
1- Extract the software by using HuaweiUpdateExtractor " Easy to Use "
open it and select your UPDATE.APP and select these Three items with right click you will find " Extract "
- recovery.img
- boot.img
-system.img
you should Extract in the same ADB Folder . it will look like this
Then :
2- Now do these Steps as its mentioned one by one :
fastboot flash recovery recovery.img
Then Press Enter
fastboot flash boot boot.img
Then Press Enter
fastboot flash system system.img
* the system.img will take a while so don't Be afraid :fingers-crossed:
* After each command it will say " OK "
3- use this relocking command " Fastboot oem relock XXXXXXXXXXXXX "
X= your Unlock Number.
TDAAAAAAAAAAAAAAAAAAAA :laugh:
Congrats. your Bootloader Is relocked :good:
waiting for your comments Guys
Click to expand...
Click to collapse
Huawei Update Extractor is officially available on xda you know ...

worstenbrood said:
Huawei Update Extractor is officially available on xda you know ...
Click to expand...
Click to collapse
Well I didn't notice that. Thank you

Hello,
try ist, but after "fastboot oem relock xxxxxx --> get this:
FAILED <remote: data parse fail>
Did anyóne know whats wrong?

bvt-1 said:
Hello,
try ist, but after "fastboot oem relock xxxxxx --> get this:
FAILED <remote: data parse fail>
Did anyóne know whats wrong?
Click to expand...
Click to collapse
What a recovery is installed?

cargobr151 said:
What a recovery is installed?
Click to expand...
Click to collapse
... send from hell, hahahahahaaaa ...
Stock-recovery ...
Did it exactly like shown in first post,I think
And surely the code is right...

Try Backup & restore -> Factory data reset from settings menu. (german: Sichern & zurücksetzen)
This wipes all include internal storage but not the external sd card.

I'll try it, thx for your help
... send from hell, hahahahahaaaa ...

I keep getting this error: failed remote: images sign check fail

please help me
MADOLOGY said:
U did something wrong then retry and do it by order u wint get it any error
Click to expand...
Click to collapse
got error root type is risk please help me

pooyan25 said:
got error root type is risk please help me
Click to expand...
Click to collapse
Same here, tried everything as advised but Nothing.

Guys ?
What is the point of re-locking bootloader ??

So the warranty is working if bootloader is relocked???

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed ​
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_edl-v2.zip from Here.
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3. ​
Proof:
Thanks to @emuzychenko for the Idea!

This is AWESOME!! Just tested and worked amazingly.
Thank you!
Edit: the included command prompt didn't work for me though, launched standard and traversed to this folder

It would've been better if the source of this guide is also mentioned, just my thoughts
Sent from my Redmi Note 3 using XDA-Developers mobile app

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned
Click to expand...
Click to collapse
Especially since most of text had been copied "as is".

Please add this to op
=> https://youtu.be/-6uErg52nKs

kaushal64 said:
Please add this to op
=> https://youtu.be/-6uErg52nKs
Click to expand...
Click to collapse
I have updated the fastboot.exe and the method also. Update your video with this and I will add it to OP.

I had replaced link for modified fastboot file please add it to op.

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned, just my thoughts
Click to expand...
Click to collapse
emuzychenko said:
Especially since most of text had been copied "as is".
Click to expand...
Click to collapse
Thumbs up!

This is great
My problem solved
Many thanks

not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.

BRoy_98 said:
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
Click to expand...
Click to collapse
Where to find it?

Zarko007 said:
Where to find it?
Click to expand...
Click to collapse
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.

BRoy_98 said:
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
Click to expand...
Click to collapse
Maybe stupid question, but wouldn't phone go to edl mode (with red led flashing) before flashing rom and what then mbn file has to do? According to your manual it is the last step?
thanks

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk

sator02 said:
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
Don't use this tool if your device is not bricked, your rom is a distributor rom that's why you cannot unlock your device, you have to flash miui rom prior to unlocking, you can do it thru edl mode using adb, search on miui forums and you'll find it.
Edit: check this out: http://en.miui.com/thread-235865-1-1.html
Sent from my kenzo using Tapatalk

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.

BRoy_98 said:
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
Click to expand...
Click to collapse
I have tried it already many Times but no success...

Zarko007 said:
I have tried it already many Times but no success...
Click to expand...
Click to collapse
This must be driver problem. Install MI PC suite and it will install all necessary drivers. Then try it again.

fastboot flash and wipe do nothing, no error

I have an essential phone that's stuck on an old version of Lineage OS that I can't update (check for updates, updates found, none actually listed to select&install)
I'm trying to install stock android 10, but when I try to flash it in the bootloader, the command line just sits there, nothing happens, no error. This happens when using the flashall command and when trying to wipe it (fastboot -w).
Screenshot:
{
"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"
}
imgur com/a/pLTygMe
Does anyone know what I can do?

susszeus said:
I have an essential phone that's stuck on an old version of Lineage OS that I can't update (check for updates, updates found, none actually listed to select&install)
I'm trying to install stock android 10, but when I try to flash it in the bootloader, the command line just sits there, nothing happens, no error. This happens when using the flashall command and when trying to wipe it (fastboot -w).
Screenshot:
Does anyone know what I can do?
Click to expand...
Click to collapse
Do you have TWRP installed?
Sent from my Pixel 4 using Tapatalk

dazeone said:
Do you have TWRP installed?
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
I don't think so- when I boot to recovery it brings be to the lineageos recovery screen. Is there a way to tell for sure?
Sorry I am not very good with this
edit - nvm, looked it up. I do not have twrp. I take it this is required?

susszeus said:
I don't think so- when I boot to recovery it brings be to the lineageos recovery screen. Is there a way to tell for sure?
Sorry I am not very good with this
Click to expand...
Click to collapse
Download the fastboot image (latest essential build) and the ota file too.
Extract the boot image from the fastboot files downloaded
Reboot bootloader and enter command.
fastboot flash boot_b <filename> filename=the boot image you extracted from the files
Then enter command. fastboot --see-active=b
Then reboot recovery
You'll see no command.
Hold power and hit volume up.
You'll be in recovery
Select apply update adb
Then enter the command it tells you to and side load the ota
Here is my video showing another method
https://youtu.be/DaMV63D9n70
Sent from my Pixel 4 using Tapatalk

dazeone said:
Download the fastboot image (latest essential build) and the ota file too.
Extract the boot image from the fastboot files downloaded
Reboot bootloader and enter command.
fastboot flash boot_b <filename> filename=the boot image you extracted from the files
Then enter command. fastboot --see-active=b
Then reboot recovery
You'll see no command.
Hold power and hit volume up.
You'll be in recovery
Select apply update adb
Then enter the command it tells you to and side load the ota
Here is my video showing another method
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for your help! I am getting the below error when trying to flash the boot.img. (fastboot:error: Command failed). I'm thinking it might be my cable? I'm not using the usb cable that came with the phone.. I'll have to see if I have another at home.
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032
C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032>fastboot flash boot_b boot.img
Sending 'boot_b' (23885 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032>​

susszeus said:
Thank you for your help! I am getting the below error when trying to flash the boot.img. (fastboot:error: Command failed). I'm thinking it might be my cable? I'm not using the usb cable that came with the phone.. I'll have to see if I have another at home.
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032
C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032>fastboot flash boot_b boot.img
Sending 'boot_b' (23885 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\Users\Mike\Downloads\New folder\stockFB\PH1-Images-QQ1A.200105.032>​
Click to expand...
Click to collapse
Open up cmd. Drag and drop the fastboot file in the command window. After you see it say. Fastboot.exe enter flash boot_b and drag the file in there. Don't forget the spaces
https://youtu.be/ArGuM5DJGh8
Sent from my Pixel 4 using Tapatalk

dazeone said:
Open up cmd. Drag and drop the fastboot file in the command window. After you see it say. Fastboot.exe enter flash boot_b and drag the file in there. Don't forget the spaces
https://youtu.be/ArGuM5DJGh8
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
Thank you dazeone for all of your help! got it running android 10 now :good:

susszeus said:
Thank you dazeone for all of your help! got it running android 10 now :good:
Click to expand...
Click to collapse
Nice. Enjoy
Sent from my Pixel 4 using Tapatalk

Magisk for Android 12/OOS12 global ( magisk_patched)

Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
How exactly do we
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Just flash this via fastboot?

scorpio76r said:
How exactly do we
Just flash this via fastboot?
Click to expand...
Click to collapse
fastboot flash boot boot.img

suhuf said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
If you're sure the version is global, it should work.

{
"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"
}

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
Read the explanation and remove the original boot file and fastboot, the phone will boot.
Put the same boot file in the download section of the phone and patch it with magisk, then upload the patched file to the phone with fastboot process.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com

Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
I also got stuck on fastboot. Any solution will be appreciated.
Edit: Had to restore device with MSM Download Tool.

Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
edit: just checked on fastboot mode. it says unlocked in red letters. would still like to flash magisk!

cjvzla said:
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
Click to expand...
Click to collapse
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.

scorpio76r said:
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
Click to expand...
Click to collapse
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?

cjvzla said:
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
Click to expand...
Click to collapse
Yes use fastboot twrp image from the official twrp thread. Then install twrp installer.

krakout said:
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
Click to expand...
Click to collapse
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked

cjvzla said:
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
Click to expand...
Click to collapse
I just sent you a personal message with a link that will help you out.

Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
Yes, using windows 10 pc.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
hi thanks for the tutorial, managed to extract the OOS12 stock boot img and patched it with magisk 24, but when I connect in fastboot mode and check with the fastboot devices command I get nothing, and nothing on device manager either. even tho my bootloader is unlocked and fastboot drivers are installed, the pc doesnt seem to "see" my phone?
the adb devices command does show my phone when connected and turned on.

That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?

krakout said:
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
Click to expand...
Click to collapse
looked for the latest drivers and installed those, now my devices does show up with the fastboot devices command! do I test the patched boot img first? and did you flash it normally or did you use fastboot flash boot_a and fastboot flash boot_b for the a/b partitions?