Database Users

[CLOSE THREAD PLEASE]Flash Modded ROM Through MI-Flash Tool!!

****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******
Use Android Image Kitchen to decompress and Recompress.
Unzip the whole Kitchen and ROM files through 7 Zip * mode.
Copy the "boot.img" to the Android Kitchen Unzipped Folder.
Follow the following steps:
Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)
Step 2. Open the file "fstab.qcom" via notepad / notepad++.
Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).
Step 4. Open default.prop via notepad / notepad++.
Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).
- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.adb.secure=0"
These enable OEM Unlock over Server and over Developer mode.
c. "ro.debuggable=0" to "ro.debuggable=1".
This turns on USB Debug.
d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"
This turns on ADB mode.
e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".
One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).
- Save the file. Do not change the file extension.
Step 7. Recompress these files back through repackimg.bat."
A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.
You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.
Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.
These steps take no more then 5-6 minutes, and are pretty easy.
Happy Flashing.
N.B.: I have attached the Android Kitchen File here.

Is this equivalent to unofficial unlock or the official one?

BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
Actually None. I mean not the official, nor the unofficial one.
I am on unlocked bootloader myself.
These are the steps I did to unlock my bootloader.
I have even rooted my RN3QC within 10 days from purchase.
I just wanted to unlock and have even custom TWRP 3.0.2-2.

can miflash just flash the boot.img?

meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
Nope, I tried, and it went to bootloop once and second time to mi logo.
The easiest way to install the boot.img and the recovery.img are:
If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.
Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done.
And if you want to flash boot.img, then flash through TWRP. That is the easiest method.
Safe and no bricks.
N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.

Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !

NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.

vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:

So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.

kraatus90 said:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
Click to expand...
Click to collapse
R3S it should not work, and as you confirmed it does not work.
Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.
They have changed the method to unlock on MM, so this apparently is only for LP.

vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.

abihary said:
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure

vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.

abihary said:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
Click to expand...
Click to collapse
Any day welcome.

For kenzo or hennessy?

zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo

zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.

What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.

MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.

vdbhb59 said:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
Click to expand...
Click to collapse
So you are back to a locked bootloader when you moved to 6.9.9?
And for doing that you just flashed the fastboot tgz file in edl mode?
Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?

[FIX][OP3/OP3T] DM-Verity warning fix. Works on 4.1.0!!

Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
1- Download the 4.0.2 firmware and the firmware of your current version:
OP3T files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5XzNCRVVwUVYzRms
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs[/URL]
Oxygen open beta 3:[url]https://drive.google.com/open?id=0Bzko1towAti5d3BtOEtXdk9hVTA[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5NzU5b3lDaEZfZ3M[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M[/URL]
OP3 files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5eXpXOXRUcXRoeXc
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WEtoYXd0NW1qUVk[/URL]
Oxygen open beta 12:[url]https://drive.google.com/open?id=0Bzko1towAti5aVVvNkIwTURjaE0[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP the firmware of your current OOS version.
And you are done! :highfive:

Migdilu said:
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
1- Download the two files:
[url]https://drive.google.com/open?id=0Bzko1towAti5Uld0cWp1YWdfLXM[/URL]
[url]https://drive.google.com/file/d/0Bzko1towAti5LXFUbEJwYUFFbGc/view?usp=sharing[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
Click to expand...
Click to collapse
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??

kunal1540 said:
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
Click to expand...
Click to collapse
Exactly, I'm uploading a new file correcting that. But don't worry, you flashed the 4.0.3 firmware. Thanks for the report!

Worked for me as well. Thank you.

thanks worked at my 1+3T.

working for me also on A3010.
thanks.

Please add
Code:
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");
as first line in your updater-script which prevents bricked devices.

Nice to see it's working!
sniperle said:
Please add
as first line in your updater-script which prevents bricked devices.
Click to expand...
Click to collapse
I'll check that later, thanks!

I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.

done it with 4.0.2 rooted and without succes

Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.

nitramcek said:
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
Click to expand...
Click to collapse
You did something wrong. Do you have 3 or 3t?

nitramcek said:
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
Click to expand...
Click to collapse
Its on oneplus 3t forum.. Can you boot to booloader?

madmax28011980 said:
done it with 4.0.2 rooted and without succes
Click to expand...
Click to collapse
Just do step 3 and 4 if you are on 4.0.2 or older. Now flash 4.0.2 firmware and then do 3 and 4 and you are done.

off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.

Migdilu said:
Its on oneplus 3t forum.. Can you boot to booloader?
Click to expand...
Click to collapse
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.

nitramcek said:
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
Click to expand...
Click to collapse
I'm sorry. Make a thread on oneplus 3 forum explaining that you accidentally flashed 3T firmware, maybe someone has a solution for this.
EDIT: Take a look at the unbrick guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Snappiestjack said:
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Click to expand...
Click to collapse
Not sure what/if I've done wrong TBH... still, I had the message

I reflashed op3t recovery i then reflashed oxygen 4.0.2 but still getting the error then i flashed twrp 3. and then the su after that i have flashed your 4.0.2. Img and gave the fastboot commands still the error is there maybe i do something wrong! The weird is that when i enter twrp it asks me for a pattern... Should i remove security locks from oxygen 4.0.2 and try again! Anyway.. Goodnight for now.

It's worked!!!
thx a lot!!!

How to Root Huawei Y6 2018 - ATU-XXX

Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Hey.
In this tutorial i will show you how to root Huawei Y6 2018.
Devices that should work:
ATU-L11
ATU-L21
ATU-L22
ATU-L23
ATU-L31
ATU-L42
YGN-AL00
YGN-L21
YGN-L22
YGN-L23
YGN-L41
YGN-L42
YGN-L51
YGN-L61
YGN-TL10
First you need to have the bootloader unlocked and usb debugging enabled.
Download this Magisk Patched Ramdisk from here: https://mega.nz/#!OdpDiKJb!MBjuu0fbjqSuynxGZ9n0x9JuoqXcV5YYXoZOvOaYAbU
After that go into fastboot and type: fastboot flash ramdisk ramdisk.img
Now type fastboot reboot. Wait your phone to boot and now it should be rooted
(You might have to install Magisk Manager mannualy to propretly use root permissions)
Tested only on ATU-L21, use at your own risk!
Tested only on EMUI 8. I'm not sure if it would work on Lineage 15.0
Original Ramdisk: https://mega.nz/#!bdwTiD5I!STHIWQrCle_nCoPKe4_Mgvo9z_Qn4Etnnhbt0fmG1PE
Kernel.img, if your phone shows Huawei logo and then goes blackscreen: https://mega.nz/#!KAoR3KYT!ufZv7ZbBsB_Bf9Rw_7vovbGJMmsuPOpUeIAFgUohKE0
If something goes wrong, you could try to flash this one.
Tutorial for noobs here: https://forum.xda-developers.com/hu...i-y6-2018-atu-xxx-t3815407/page3#post77139034
If i helped, press the Thanks button
(I don't own the device)

t-mobile_mda said:
hey guys again..
or u can share modemst parts...
fsc -> /dev/block/mmcblk0p15
fsg -> /dev/block/mmcblk0p24
modemst1 -> /dev/block/mmcblk0p32
modemst2 -> /dev/block/mmcblk0p33
Read..
dd if=/dev/block/mmcblk0p15 of=/sdcard/mmcblk0p15
dd if=/dev/block/mmcblk0p24 of=/sdcard/mmcblk0p24
dd if=/dev/block/mmcblk0p32 of=/sdcard/mmcblk0p32
dd if=/dev/block/mmcblk0p33 of=/sdcard/mmcblk0p33
tia...
Click to expand...
Click to collapse
i can help you with this, i need an good EFS backup, just help me with how can i activate diag for backup the qcn, i have the ATU-L42 model, it is the same board.
i will root my device and try to activate diag.
here are the backups you asked for, are from a locked ATU-L42

I won't recommend to install it on ATU-Lxx because it's build for The L21, every bootimage of all ATU devices are different except L22 and. L22, so you might soft brick your phone. But still thanks for your tutorial.

iDecrypt said:
I won't recommend to install it on ATU-Lxx because it's build for The L21, every bootimage of all ATU devices are different except L22 and. L22, so you might soft brick your phone. But still thanks for your tutorial.
Click to expand...
Click to collapse
One friend of mine, Runner85sx, looked into your device Kernel and veryifed what models of the Y6 2018 should be compatibile with this root method.
Thread updated, with the devices that will root sucesfully with this method.

Thespartann said:
One friend of mine, Runner85sx, looked into your device Kernel and veryifed what models of the Y6 2018 should be compatibile with this root method.
Thread updated, with the devices that will root sucesfully with this method.
Click to expand...
Click to collapse
Thanks for updating your thread

how to unlock bootloader? mine is ATU-L22

brixnix said:
how to unlock bootloader? mine is ATU-L22
Click to expand...
Click to collapse
This is not the place to ask these things at all...
To unlock your bootloader you will need to get your Bootloader unlock code, witch huawei doesen't provide anymore, from what i know. So you will have to use something like DC-Unlocker and pay to get your bootloader unlock code. After you got your bl unlock code you should install HiSuite, Minimal adb and fastboot on your PC. After that enable USB Debugging and OEM Unlock from your device developer settings.
Now connect your device to your PC and type this in Minimal adb and fastboot console:
Code:
adb devices
Now accept any dialog that will show up on your phone. If your device is recognised then type
Code:
adb reboot bootloader
Then write
Code:
fastboot devices
To see if your device is recognised while in fastboot, and if it is type
Code:
fastboot oem unlock (bl unlock code)
That's it.
For any futher help make a thread on Huawei Y6 Questions and Answers please.
If i hepled press the Thanks button

Do you have recovery for Y6 2018 (ATU-L22) like TWRP or CWM Recovery?

TsunaXZ said:
Do you have recovery for Y6 2018 (ATU-L22) like TWRP or CWM Recovery?
Click to expand...
Click to collapse
THIS IS NOT THE THREAD TO ASK THAT.
If i had i would share it on the forums. As you see there are no recoveries for the Y6 2018.

Thespartann said:
THIS IS NOT THE THREAD TO ASK THAT.
If i had i would share it on the forums. As you see there are no recoveries for the Y6 2018.
Click to expand...
Click to collapse
Sorry just got curious.. thanks for the guide btw but there is a problem, I cannot access any google application like playstore,gmail, & etc,. I can't also add Google account because it loads forever and at the end it says: "Couldn't sign in". Need help please Thanks!

After updating inside magisk app the phone won't work it just shows "Huawei" then blackscreen.

TsunaXZ said:
After updating inside magisk app the phone won't work it just shows "Huawei" then blackscreen.
Click to expand...
Click to collapse
Could you please be more explicit?
So you rooted your phone with this method, and after you applied a update to Magisk? or Magisk Manager now your phone wont boot?
Also what happens when you want to acces play store?

Thespartann said:
Could you please be more explicit?
So you rooted your phone with this method, and after you applied a update to Magisk? or Magisk Manager now your phone wont boot?
Also what happens when you want to acces play store?
Click to expand...
Click to collapse
Yes I rooted my phone with this guide and the root access works at first playstore still works connected with my Google account so I tried to remove it but when I try to add any google account it just keep loading, Gmail loads forever. after that I tried to update the Magisk inside the manager which got success but when i boot it up. It just shows "Huawei" then turn off.

TsunaXZ said:
Yes I rooted my phone with this guide and the root access works at first playstore still works connected with my Google account so I tried to remove it but when I try to add any google account it just keep loading, Gmail loads forever. after that I tried to update the Magisk inside the manager which got success but when i boot it up. It just shows "Huawei" then turn off.
Click to expand...
Click to collapse
I see. You could try to flash the original ramdisk from fastboot just like you flashed the patched ramdisk.
Download link: https://mega.nz/#!bdwTiD5I!STHIWQrCle_nCoPKe4_Mgvo9z_Qn4Etnnhbt0fmG1PE
Why you wanted to remove it? x)
You could maybe uninstall all google stuff and install MicroG/Reinstall Gapps. Or restore Emui's system.
I think you should give a try to iDecript's Lineage 15.0 Rom.
Link: https://forum.xda-developers.com/huawei-y6/development/rom-lineageos-15-0-huawei-y6-2018-t3811575

Thespartann said:
I see. You could try to flash the original ramdisk from fastboot just like you flashed the patched ramdisk.
Download link: https://mega.nz/#!bdwTiD5I!STHIWQrCle_nCoPKe4_Mgvo9z_Qn4Etnnhbt0fmG1PE
Why you wanted to remove it? x)
You could maybe uninstall all google stuff and install MicroG/Reinstall Gapps. Or restore Emui's system.
I think you should give a try to iDecript's Lineage 15.0 Rom.
Link: https://forum.xda-developers.com/huawei-y6/development/rom-lineageos-15-0-huawei-y6-2018-t3811575
Click to expand...
Click to collapse
Well I accidentally deleted it because my mails on my Gmail won't load but that doesn't work. Actually I'm already downloading Lineage OS with Gapps & SuperSu by iDecrypt. I'm hoping it is much snappier than EMUI 8.0.0. Fact is this is my first phone from Huawei right after I got my Galaxy note 4 lcd broke which cost half of the phone itself lol. So I'd rather buy a new phone than replacing the old one. :3
Restore EMUI system? how? is that on eRecovery? the only option on it was 1.)"Download latest version and recovery"which doesn't work 2.)"Wipe data/factory reset" 3.)Reboot 4.)Shutdown
Do you have stock rom for this model? cuz I can't seem to find one for this. Thanks for your time btw
I tried the first link you provide which is ramdisk but that doesn't help either.

TsunaXZ said:
Well I accidentally deleted it because my mails on my Gmail won't load but that doesn't work. Actually I'm already downloading Lineage OS with Gapps & SuperSu by iDecrypt. I'm hoping it is much snappier than EMUI 8.0.0. Fact is this is my first phone from Huawei right after I got my Galaxy note 4 lcd broke which cost half of the phone itself lol. So I'd rather buy a new phone than replacing the old one. :3
Restore EMUI system? how? is that on eRecovery? the only option on it was 1.)"Download latest version and recovery"which doesn't work 2.)"Wipe data/factory reset" 3.)Reboot 4.)Shutdown
Do you have stock rom for this model? cuz I can't seem to find one for this. Thanks for your time btw
Click to expand...
Click to collapse
Here is the Stock Rom for ATU-L21. I know you own an ATU-L22 but from what i know it should work perfectly with your model too.
Download link: http://huawei-firmware.com/rom/huawei-y6-2018/atu-l21/19931
I will upload it to MEGA later today, as the download speed is much better on Mega.
Yeah well from now i don't recommend Huawei Phones anymore as they don't provide Bootloader Unlock codes anymore.
Instructions on restoring Stock should be avalabile on the same page that i sent you for downloading.
As of my time, well if i made this thread i should also help people that had issues
As i don't have the device and i'm not really used to Treble i'm not yet providing treble Roms for this device. But i might be doing that in the future.

Thespartann said:
As i don't have the device and i'm not really used to Treble i'm not yet providing treble Roms for this device. But i might be doing that in the future.
Click to expand...
Click to collapse
I'm looking forward into that :good:
Do you think iDecrypt's LoS 15.0 would fix my problem? cuz I'm halfway of the download.

I tried downloading the link you've provided of the stock rom and I got the "UPDATE.ZIP" inside there's a file called UPDATE.APP what should I do? need help Thanks!
If I'm correct there is a 2 methods which is: SD card method and by using Fastboot

TsunaXZ said:
I tried downloading the link you've provided of the stock rom and I got the "UPDATE.ZIP" inside there's a file called UPDATE.APP what should I do? need help Thanks!
If I'm correct there is a 2 methods which is: SD card method and by using Fastboot
Click to expand...
Click to collapse
You should try to use erecovery to install it.
Put that update.zip in dload folder on sdcard/internal. Then press power vol up vol down when your phone is not on.

Thespartann said:
You should try to use erecovery to install it.
Put that update.zip in dload folder on sdcard/internal. Then press power vol up vol down when your phone is not on.
Click to expand...
Click to collapse
The problem is the phone is bricked, Yes I can access eRecovery but computer doesn't recognize it both internal & external.

TsunaXZ said:
The problem is the phone is bricked, Yes I can access eRecovery but computer doesn't recognize it both internal & external.
Click to expand...
Click to collapse
Just insert a sdcard and place the dload folder containing the update.zip then. Is it recognised in fastboot? Then why don't you flash LineageOS to make the phone usable for a while.
There is another option. Get the update. app and extract it with huawei update extractor. Then go into fastboot and flash ramdisk, kernel and everything you can flash from that.
Example: fastboot flash kernel kernel.img
Didn't quite have time for helping more.

11.0.8.8 Rooting Issue

I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?

Remove oos native call recorder module if you have it, if not just remove all modules.

MrEvilPanda said:
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Click to expand...
Click to collapse
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..

dladz said:
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
Click to expand...
Click to collapse
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.

MrEvilPanda said:
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
Click to expand...
Click to collapse
Ah yes, always disable Magisk modules prior to upgrading firmware.
As they may not be compatible, this is also in the guide.
Glad you're up and running mate
Nice one

So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??

Arksuga said:
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Click to expand...
Click to collapse
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

galaxys said:
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):

Arksuga said:
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Click to expand...
Click to collapse
Yep I've got guides for unlocking the bootloader and rooting in the guides sections.
Both called as such accordingly.
Tbh there are a few guides all should be fine.
Just read through the root guide.
Unlocking the bootloader it's easy.
Code: fastboot OEM unlock
Agree on phone.
Rooting:
Obtain patched image
Fastboot boot Magisk patched
Don't flash it, just wait for boot then open Magisk and click install / direct install.
Again this is all in the guides.

Question Magisk direct install not visible

Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
You could try searching "direct install not visible in Magisk".

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Are you sure you booted the right boot image?

Try with this one:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I think the magisk patched 1.5.2 is not really patched or there are some checks in place that allow only certain imgs to work
If it still does not work, download the stock boot, patch it with magisk select that boot img, fastboot, boot the new patched img

TheNewHEROBRINE said:
Are you sure you booted the right boot image?
Click to expand...
Click to collapse
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images

AnotherM1m said:
Try with this one:
Click to expand...
Click to collapse
You didnt attach something

paper88 said:
You didnt attach something
Click to expand...
Click to collapse
shift enter is a special combination here on xda i've edited my previous message

AnotherM1m said:
shift enter is a special combination here on xda i've edited my previous message
Click to expand...
Click to collapse
Still no success. I just think I broke something while I did the OTA and I just need to wait till the next update. I restored first the images and installed it over OTA, after restart the update was not installed but Magisk deinstalled. Then I installed it again and restarted it and wanted to flash boot.img, but since then its not working anymore

what command on the terminal are you using for boot.img?

AnotherM1m said:
what command on the terminal are you using for boot.img?
Click to expand...
Click to collapse
Tried fastboot boot img and fastboot flash boot img

paper88 said:
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images
Click to expand...
Click to collapse
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?

paper88 said:
Tried fastboot boot img and fastboot flash boot img
Click to expand...
Click to collapse
Are you on a global device or eea?
Have you tried patching the img yourself?

TheNewHEROBRINE said:
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?
Click to expand...
Click to collapse
AnotherM1m said:
Are you on a global device or eea?
Have you tried patching the img yourself?
Click to expand...
Click to collapse
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m

paper88 said:
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m
Click to expand...
Click to collapse
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?

AnotherM1m said:
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?
Click to expand...
Click to collapse
Its Spacewar EEA

paper88 said:
Its Spacewar EEA
Click to expand...
Click to collapse
Ok, the problem is that we just discovered 1.5.2 is not unified at all.
Those images are not working because they are dumped from a global device.
You need a modified eea image which i cannot find for now...

I did root my 1.5.2 EEA without issues with a self-patched 1.5.2 Stock from https://forum.xda-developers.com/t/...g-os-repo-of-nothing-os.4464039/post-87101175

Since you are very fortunate that this device has usable EDL mode, you can always dump your boot image on any firmware you're by using the EDL tool made by @mark332. (However, I suggest you try following @dedors suggestion first).

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.

ethical_haquer said:
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.
Click to expand...
Click to collapse
What did I do wrong? I do it like this since 12 months on oneplus and nothing