Related
UPDATED to include instructions for flashing other ROMS
I've successfully unlocked, flashed TWRP, rooted, and flashed Lineage on both an XT1602 and an XT1607. I'd done this before on other devices, but had forgotten just how it all came together, so when I was done I went back and made this step-by-step guide. It's a bit shorthand.
Many thanks to squid2 for his TWRP port, to the folks who make superuser, to parrotgeek1 for superSUFixer.zip, and to spiked_mistborn for reminding me about it. And, of course, huge thanks to squid2 and Alberto97 for the killer Lineage ROM. It is far better than stock or the last Nougat CM. If I forgot anyone, or made any mistakes here, somebody please point them out. Have fun!
1. Preparation (if the links don't work, search on xdaDevelopers or with Google)
a. Backup entire phone to the extent you are able, either with a dedicated tool and/or to Google via the Android backup feature
b. Download and install Motorola Device Manager on your computer from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 so as to make sure you have the proper drivers
c. Download adb and fastboot tools onto your computer from
http://forum.xda-developers.com/showthread.php?t=2588979 or
http://forum.xda-developers.com/showthread.php?t=2317790d. Download TWRP for Moto G4 Play to same folder as adb and fastboot tools from http://forum.xda-developers.com/devdb/project/?id=16870#downloads
e. Depending upon whether you want to flash Lineage or stay with the stock ROM, download to the same directory on your computer either:
i. Lineage and the Lineage SU addon (if you want root) from https://forum.xda-developers.com/g4-play/development/rom-lineageos-14-1-moto-g4-play-t3544646 and Google apps (arm 7.1 micro) from http://opengapps.org/; or,
ii. superSUFixer.zip from http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396 and superusersu.zip from http://www.supersu.com/download
Note: I did not find superSUFixer.zip necessary when I intially rooted, but after later installing squid's kernel it was indispensable to reinstallation of superusersu.zip.g. Attach phone to computer with USB cable, enable file transfer on phone and either copy the Lineage zip and Lineage SU addon zip and gapps.zip to your phone, OR copy superSUFixer.zip and superusersu.zip to the phone (you don't need to copy twrp)
2. Unlock bootloader
a. Enable developer options (Settings/About Phone/tap Build Number 7x)
b. Enable USB debugging on phone (Settings/Developer Options)
c. Enable OEM unlock on phone (same)
d. Open command window and change to the directory where you put adb, fastboot, and twrp
e. > adb devices (to check that you are connected - you should get a response with a device id)
f. > adb reboot bootloader
g. >fastboot oem get_unlock_data
h. On computer, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (you need to proceed through the login and to the second page)
i. Copy data returned by phone in the command window (make sure you copy all of it!)
ii. Paste that data into the Data Scrub Tool on the web page
iii. Copy scrubbed data, paste it into the box on the web page at step 6, and click the button; if it says you can't unlock your device, either you didn't copy and paste all the data, or your phone can't be unlocked and you're done; otherwise,i. Copy unlock key from email
j. > fastboot oem unlock <unique unlock key>
3. Flash TWRP
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
4. Flash Lineage and root, or just root -- when the phone has rebooted into recovery (you'll be in TWRP now)
a. follow prompts to make TWRP permanent or not
b. DO A FULL BACKUP OF EVERYTHING with TWRP
c. make sure you performed step b (or you may wish you had later, if something goes wrong!)
d. To flash another ROM, in TWRP
i. Wipe Data, Cache, and Dalvik. (Yes, you have to do this.)
ii. For Lineage - Install the Lineage zip file, the Lineage SU addon zip file, and the gapps zip file, one after the other, in that order, WITHOUT REBOOTING in between. TWRP will let you add all three to its queue to flash in order;
iii. For other ROMs - see instructions for those ROMs, but in general, install the ROM zip file, and then the gapps zip file, one after the other without rebooting in between. For root access, depending on the ROM, you may need superSUFixer, supersu.zip, or both; again, see the instructions for the ROM you are flashing.OR
e. To stick with the stock ROM but get root access, DO NOT WIPE, just flash superSUFixer and then supersu.zip
5. If TWRP does not automatically reboot your phone (if you unchecked the "reboot when done" box), then reboot to the System; if you left the box checked, then your device will reboot by itself once the zip files have been flashed.
6. Follow the prompts to set up your new ROM or stock Android.
7. Reboot into recovery (TWRP) and make another backup!
8. Want to get rid of the "Unlocked Bootloader!" warning screen? Flashing this file from TWRP worked for me (all the others I tried did not work):
https://forum.xda-developers.com/attachment.php?attachmentid=4065906&d=1488923356
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
fireball0093 said:
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
Click to expand...
Click to collapse
Any word yet on that unlock code?
loociddreemr said:
Any word yet on that unlock code?
Click to expand...
Click to collapse
After talking to their customer support, I never got an email. The next day however I decided to go online to their boot loader page and put my code in, then it worked! The data scrub tool or whatever it may be called that they have I recommend using it too.
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Thanks a ton for the guide
haher2 said:
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Click to expand...
Click to collapse
They are in a subdirectory of the TWRP directory. With the proper drivers installed on your PC you can transfer them via File Explorer. Or, 20 pounds/euros/dollars will get you a 64gb SD card.
3. Flash twrp
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
Click to expand...
Click to collapse
I tried to fastboot boot recovery from the bootoader but it didn't work. I rebooted the phone first and did it with: "adb reboot recovery" in windows.
Overall nice guide, works like a charm, i also flashed the unlocked bootloader warning with a custom logo.bin, no issues here and works like a charm (I flashed it with the stock logo you see when you first bought the phone with a locked bootloader)
Thank you!
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
loonix said:
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
Click to expand...
Click to collapse
Yes and, adding to what you said, you need to re-enable the "Allow bootloader unlocking" and "USB Debugging" in Developer Settings if you failed to flash your recovery as the device expects to be flashed. Else, you'll get a "unable to load kernel" error in the bootloader log and being rebooted again to the bootloader menu.
Great tutorial indeed, thanks a lot. Nandroid backup doesn't worked for me but i'm going on.
Edit - worked after disable sd as internal memory
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
hamelg said:
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
Click to expand...
Click to collapse
In concept, I don't see any reason why you couldn't use TWRP to flash the stock ROM and then fastboot to flash the stock recovery ... or fastboot to flash both (be easier and quicker). The Moto website may have instructions for re-locking.
mkollersms said:
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
Click to expand...
Click to collapse
In a command window use the cd command to change directories. For example:
C:> CD \mytopdirectory\mysubdirectory
Another link to consider about OTA update if you stick with the stock ROM :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
Thanks again.
If your phone is from Verizon Prepaid, Moto will say the device is not eligible to be unlocked. Knowing Verizon, it's not likely to be unlocked later along down the line either. Hopefully someone comes up with a good way to bypass this restriction and install some ROMs.
Does this method work on the Verizon prepaid model, or does it have to be from moto/amazon?
Moto g play twrp IMG file not IMG it's **** IMG file please develop it
Does this works with LATAM version? XT1601?
Thanks :good:
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.
Hi all,
please find attached the Havoc OS 3.8 custom ROM, Olivelite version, and Magisk 20.4 which you will need for installation also.
I am neither the creator of this ROM or anyhow involved with the team, nor do I take any responsibility for everything which might go wrong during installation.
How I got it to work:
1. Unlock your boot loader (you will find appropriate instructions here in the forum and elsewhere on the web, also on YouTube).
2. Ensure that you have the XiaoMi Flash tool and the latest stock rom available, to be able to recover you phone when you encounter issues.
Both can be found on the Xiaomi website.
3. Get the "minimal ADB and Fastboot" tools. You will find in the web.
4. Get TWRP (you will find out what this is and why you need it here in the forum). Take care that it is a version for your phone model, else worst case it will not work.
5. Put the attached files to an external SD card in your phone.
6. install TWRP. Boot into "Fastboot" mode and install TWRP with command "fastboot flash recovery twrp.img".
7. Boot into recovery mode - if yoiu did everything right, should be TWRP now
7a. Wipe - Format data - confirm with "Yes", then go back to main menu
7b. Wipe - advanced wipe - select all except the last 2 (expecially NOT "external SD" if you put your files on there),
go back to main menu
7c. Install - select location where you've put the "havoc 3.8 update.zip" and select the file, afterwards wipe Cache / Dalvik (TWRP will give you this option after install), DO NOT REBOOT
7d. Install - select location where you've put the "magisk v20.4.zip" and select the file, afterwards wipe Cache / Dalvik and then reboot to system.
Now, hopefully, congratulations and enjoy
If something happens and it will not work at all, search the web first for solutions and, if still does not work and you do not get along with it, do not worry. You can always go back to the Xiaomi original ROM with the XiaoMi Flash Tool. Phone must be in "Fastboot" mode for this. In the flash tool, select your ROM location (ideally in the root of your drive as this tool cannot interpret spaces in paths), then confirm and ensure that you have ticked "Clean all" in the bottom, NOT "clean all and lock" - else you will have to do the unlock procedure again.
Sometimes, you need the "permissiver v5.zip" which you will find on the web. In case the above does not work, you can try to install the Permissiver. I never needed it, and I'm using 2 Redmi Olivelite.
I just tried this and had a success message from TWRP about the Havoc 3.8 flash but the Majisk file had an error from within TWRP first time & then it installed after reboot. But I still go straight into TWRP after rebooting.
Right now I have TWRP on the device & a micro SD card to get files onto the device but no OS on it & no backup as one way or another I want a ROOTed OS & it was the Chinese version when I got the phone so useless to me anyway.
What's the best approach from here to get this thing running again?
Thanks!!! Thanks!!! Thanks!!! after trying to get a GSI rom run on my daugthers olivelite i finally got a new rom working. I don't know why last guides didn'twork for me actually a recently requested a boot.img patch but i managed to patch it myself after dealing with python. Now will try to update it to 3.12 i suppouse it iwll have many improvements. But this worked right out of the box for me. Just followed each step and good to go.
For anyone interested. its de 2Gb/32Gb Global Version. with 12.0.3 latest MIUI updated applied trough fastboot. I used OFOX to test it and it worked fine by now.
If you have guide to update HAVOC please point me in the right direction.
Thanks again
I got off .Havoc precisely because it did not have voLTE support & BT HS 's didn't work. Has anyone had any luck on these 2
I absolutely thank you for this rom, I can now miraculously play Asphalt 9 on high settings at 30ish fps while on miui it struggled on lowest settings, the UI is flawless but I only have one problem I can't send nor receive SMS and the phone sometimes reboots randomly but that cannot make me go back to miui since it's too heavy for my phone.
IS THERE any fix for not being able to receive or send SMS
I have a black screen [FIxed by installing OrangeFox recovery]