'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
You could just test the code in fastboot: fastboot oem unlock UNLOCKCODE
If the code is incorrect, for some reason, it will say Password incorrect. Else it will bring you to the yes/no unlock screen on phone. DCs unlock code should always work as it doesn't need the correct imei/imei2/sn/product combo when generating unlock code.
There's no real point in staying on xloader 01 anymore, every update (except a few unapproved firmware) after 02 started appearing has been 02.
Downside is that you can't downgrade, but you could replace fastboot in latest fw with the one from may/June and you'd have DC working again. But there's also service firmware available for free on androidhost.ru which can be used if phone should brick. There's also testpoint (only one person has tested this) which can be used to downgrade to any firmware (even xloader 02 to 01).
Before unlocking, backup everything as unlocking will wipe data.
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
ums1405 said:
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
Click to expand...
Click to collapse
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
debbuger said:
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Click to expand...
Click to collapse
Thanks, that's worth the entrance fee alone as they say.
Pretoriano80 said:
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
Click to expand...
Click to collapse
Thank you for taking the time to put me right.
I'll go back to your Unofficial TWRP post and go through it A to Z.
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
ums1405 said:
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
Click to expand...
Click to collapse
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
ums1405 said:
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
Click to expand...
Click to collapse
Well, you can't stay on xloader01 forever, at least not if you want to update your device.
The cons is that once on xloader02, you can't go back to xloader01.
Pretoriano80 said:
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Click to expand...
Click to collapse
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
ums1405 said:
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
Click to expand...
Click to collapse
All except userdata, system and vendor (these are large and can be found on stock firmwares, so can be skipped).
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
ums1405 said:
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
Click to expand...
Click to collapse
You can use HWOTA8 or HuRUpdater! Beware that if you update to a firmware with patch 01, simply flashing Magisk won't work anymore and you will have to patch the stock ramdisk with Magisk Manage (keep encryption and preserve dm_verity must be enabled) , then flash the patched image with fastboot.
Related
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
Hey XDA, I haven't been on here since my Samsung S2 years ago. I picked up a new moto Z for daydream, (amazon 499 special, 64 gb luna grey unlocked, retus software, 650-03). I bought it from the american amazon, and I am in canada. I popped in my Sasktel sim card and it works perfectly.
My questions are:
How do I manually flash nougat?
If I flash to the rogers 45 firmware, will I still be able to use my Sasktel sim?
How long until nougat comes out regardless? Should I just wait?
If I do flash to this "rogers 45 nougat", can I go back to my "vanilla" stock later? ( i just want daydream now, i bought the headset already. then when my area gets nougat, ill flash back to my phones nougat.. or does it make a difference?)
Sorry for the really random questions. I couldn't find the answers to these on the forums or on google. (reddit has been saying just wait, and don't flash)
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
pixelens said:
...
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
enetec said:
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
Click to expand...
Click to collapse
Going to start a new thread so as not to hijack this one
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own - opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Yes very good tutorial, I really likes to write something like this but I'm not good in English
Thanks again
erfanoabdi said:
...
Thanks again
Click to expand...
Click to collapse
Ahahahaha, this is only "chatting" in not-so-good-English ... :laugh:
Thanx for you *great* development here instead! :highfive:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Wow! Thank you for the response! This answered pretty much all of my questions, but also sparked a few more. The Moto Z was a pretty big purchase for me so I am in no hurry to lose functionality. A lot of people are using translators on here, so I'll be simple (sorry if it comes off as blunt or rude, typing with translators in mind)
I want to stay on android 7. Downgrading to 6.0 is not a worry for me.
I want to get future updates from my carrier. (official android/moto updates and security patches. I want to be able to use the "Google Tango" mod, if it comes out)
I want to be able to use the projector mod and daydream.
I do not plan on rooting my phone (maybe later), and I do not want to unlock my bootloader.
Will the retmx nougat be different then the copy of nougat I would get from retus?
Finally, is there any benefit to waiting for the OTA? Or am I getting the exact same copy of nougat on XDA, that I would in three weeks from OTA? I already bought the daydream headset, am I waiting for nothing?
*two more questions I guess*
Do I need a SD card?
do I need to unlock my bootloader to do this upgrade?
( http://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095)
(http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245)
Sorry for all the questions. I have looked all over XDA and haven't been able to find an answer (reddit, and google too :/). I am hoping that other people will be able to read this, and have their questions answered as well.
Again, thank you. You guys are really smart.
pixelens said:
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Porcelainfog said:
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Click to expand...
Click to collapse
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Based on your expressed needs... I'll just wait your OTA. Nothing more. It's only a matter of weeks anyway...
Sorry for being a newb and asking here but I'm finding it difficult to get my head around this.
I was originally on MM and upgraded to Nougat on unlocked I international Moto Z.
I then decided to install TWRP, root and try a new ROM. If I want to go back to stock Nougat can't it just be a case of flashing the Nougat update I have download on my computer through ODIN or is it going to be a little more complex than that?
Thanks for any help
pixelens said:
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Click to expand...
Click to collapse
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Porcelainfog said:
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Click to expand...
Click to collapse
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
pixelens said:
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
Click to expand...
Click to collapse
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Dawnhawk said:
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Click to expand...
Click to collapse
LOL, of course they did!
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Porcelainfog said:
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Click to expand...
Click to collapse
Cool. And ya re ADB haha
Hello everybody.
I have a simple Question about root on this model, is it possible to do?
And if it is possible, tell me how Please.
Best regards
Wojtek
I am looking for the same too
Me too... Looks like it is still impossible
Only paid method and who knows it will be work on my p30 lite......hmm
Hello ppl,
I know this might be a little old.. any way just for the knowledge lets bring this thread back.
I had the same concern for a while, and kind of eager to get mine rooted.. until now.
I managed to unlock mine, and root it succesfully. Latest version of magisk, safty net passed, root essentials running like a charm, I can ADB in to it and su yey!
How? main issue here is my p30 lite MAR-LX3A was already in emui10, and somehow this little sucker wont allow the unlock of the bootloader regardless. I used a unlock tool that is advised to work for this model using testpoint short. how ever it was not working for me, until I read the EMUI had to be downgraded to 9.1.
Once runnig EMUI9.1 I didnt had to re-run the tool it was already unlocked. weird.
Any how the unlocker tool I used was not the ABD/fastboot tools, it was a paid app in case you are still interested in getting it done I can tell you how. Just keep in mind you will need to Open the back cover of the device.
Think is there is no custom recovery image available that works, neither a custom ROM, so all you have is pretty much root access.
I beleive this to be a pretty decent phone so I dont want just to ditch it, I am working to get a TWRP image, if I a managed to so I will get a ROM done as well. Think the whole device has been off the track for dedicated modders and devs, so it has just not been worked on.
which me luck. I'll keep you posted
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
aka_max said:
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
Click to expand...
Click to collapse
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
blzbh said:
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
Click to expand...
Click to collapse
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
aka_max said:
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
Click to expand...
Click to collapse
why dont you try getting an image of the partition with DD, convert it and mount it in the PC directly, I beleive using the scan software directly against the phone is more complicated than just scanning a directly attached block device.
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
i have read some posts about wipe data.. use stock rom etc... But i am to lazy to test it. Let me know if it will works. Be sure to make a backup before playing around
nominator64 said:
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
Click to expand...
Click to collapse
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
aka_max said:
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
Click to expand...
Click to collapse
agreed I have been working on one that truely works, but there are a few blanks about how TWRP really works.. and its boot process. I have learned a little this past week, but still think gonna have to reverse engineer a working img to get some answers.... I was actually thinking on building a orange fox image better not sure what would be easier..
I have lots of work so I do this in my free time, but let me know if you want a help perhaps we can get something and port a nice ROM that's worth the device
.
blzbh said:
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Click to expand...
Click to collapse
thank you for the suggestions. unfortunately does not work :-(
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
k.r.o.o.k said:
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
Click to expand...
Click to collapse
Sure, ive been busy but will try my best.. about the unlock process I end up paying 19 euros... But try using fastboot unlock first.. may save you the money not sure...
1. Downgrade to emui 9.1 .. just plug the p30 lite to PC, install hsuite... Go for the firmware/software update... A pop up screen will show up with some small letters buttom rigth.. older releases or revert to older firmware something like that.. you will get too choose 9.1 only ... Choose that and apply.. Keep an eye out.. this will delete everything in your phone... Next boot you will be in 9.1.. avoid the automatic upgrade.
2. Turn the phone off, take the back cover and locate the testpoints.. short by using metal wire... The small aluminium wire wraps that come with bread and other bags for easy close are usefull just remove some plastic in each side... connect the usb cable to PC.. leave the phone side unplugged.. Touch test point with the wire while the other side touches a metal cover in the phone.. while doing it plug the phone to the USB cable.. the charging animation should not appear . . . Screen must stay black.. otherwise do it again.. if done right the device manager will detect COM port for your device
Identify the point with this video
3. use either app you want to detect testpoint mode and unlock... I managed to do it with a 3 day unlimited license for HCU client.. that did the trick their website have some tutorials easy to follow.
Hi all,
I have the same problem like a few other people. I unlocked the phone with HCU, and after I tried to root with magisk (by trwp) But the main issue, the phone is encrypted and the installation proccess of the magisk by the trwp got failed. How can I root this phone? Anybode has success with this?
Thank you!
huawei p30 lite device root support please
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Thank you, that's helpful
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Is this still the case? I read another thread that says this may be the reason it no longer works.
oromis995 said:
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
Click to expand...
Click to collapse
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
mobile_sensei said:
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
Click to expand...
Click to collapse
I meant data. I know that I need the partitions
oromis995 said:
Is this still the case? I read another thread that says this may be the reason it no longer works.
Click to expand...
Click to collapse
if you decide to use the security patch it came with stock then be sure not to connect tp the internet at all because once its unlocked and rooted and downloads an update dsu sideloader will not work until that update is dealt with and system updates wont work while bootloader unlocked and definitely not going to work if any partitions are modified(not stock such as magisk patched boot image). im not sure about the september update but some did have issues with the august patch although others were successful so it may have just been user error. my suggestion is to just put dsu sideloader and a prerooted gsi on an sdcard or transfer via pc/usb cord to internal storage but don't connect to the internet and use that to gain root long enough to pull your full stock partitions backups. this would be playing it safe. then ifnyou want you can relock your bootloader and update to september/newest and pull another full backup so you have it in the case that ypur successful and if not then your bases are covered to downgrade and downgrading will be as easy as simply reflashing all the stock images you pulled the first time though you shouldnt have to reflash ALL of them but in case you want to / need to then u have them. I cant stress backups enough. I use Partitions Backup & Restore by Wanam from playstore or wherever u want to download it unless u prefer to dd everything but i like the gui its just easier. read my post on how to root any n20 as there are somegood tips there and a great response detailing the procedure and dmtec also posted a much more detailed guide. i still havr a device on May patch and the other on July