Related
I feel like I am confused with all these terms:
Rooting the device is just elevating the default permissions to root level so you can do whatever you want, just any operation is under sudo privileges.
Recovery is a "something" that handles data wiping, installing low level packages (most likely custom roms), making backups, etc. Actually Recovery is a mode / app that user can operate without having Android installed on their phone. See TWRP or CWM.
Flashing - installing firmware thingies from low level mode (recovery / adb)
Bootloader is our OS picker, for Unix-like systems its usually GRUB, but in mobile devices it does not have a name I guess
Bootloader unlock / unlocked bootloader - I don't know nothing about that, except this is prerequisite to root the device
ROM Kernel - a Unix-like OS core, having scary versioning number like 123.456.777.888.12a-dev/rc
Stock ROM - a rom full of bloatware, we don't like stock roms
When we speak about rooting device, what is actually rooted? A bootloader? a rom? a kernel?
According to this topic, the rooting method depends on used bootloader and kernel version - how does it come together? I don't think that bootloader depends on rom kernel version as bootloader will work without any OS.
A quote from the guide: "New official updates are scheduled to be released soon and the phone has to be unrooted for them to be installed." - but I am root and I want that update right now :laugh:
Hell4Ge said:
I feel like I am confused with all these terms:
Rooting the device is just elevating the default permissions to root level so you can do whatever you want, just any operation is under sudo privileges.
Recovery is a "something" that handles data wiping, installing low level packages (most likely custom roms), making backups, etc. Actually Recovery is a mode / app that user can operate without having Android installed on their phone. See TWRP or CWM.
Flashing - installing firmware thingies from low level mode (recovery / adb)
Bootloader is our OS picker, for Unix-like systems its usually GRUB, but in mobile devices it does not have a name I guess
Bootloader unlock / unlocked bootloader - I don't know nothing about that, except this is prerequisite to root the device
ROM Kernel - a Unix-like OS core, having scary versioning number like 123.456.777.888.12a-dev/rc
Stock ROM - a rom full of bloatware, we don't like stock roms
When we speak about rooting device, what is actually rooted? A bootloader? a rom? a kernel?
According to this topic, the rooting method depends on used bootloader and kernel version - how does it come together? I don't think that bootloader depends on rom kernel version as bootloader will work without any OS.
A quote from the guide: "New official updates are scheduled to be released soon and the phone has to be unrooted for them to be installed." - but I am root and I want that update right now :laugh:
Click to expand...
Click to collapse
When you root, you root the kernel, it basically means making the kernel obedient with your demands.
Generally, when you do something that requires root privileges, if your kernel is not rooted, it will deny permission to do so, if it is rooted it will comply.
Everything you do on the phone has to get clearance from your kernel.
The second part, once the bootloader is unlocked, it does not matter what method you use to root the phone.
Rooting method is a subject to kernel version and to whatever modifications the OEM has made to it.
The third one, if your phone is detected to be rooted, the CTS certifies your device to be insecure and it will automatically block the update.
If you try to update when you are root by somehow hiding your root, you will lose root. I have also heard of some devices getting bricked during this process.
HIT THANKS IF FOUND USEFUL
Use Magisk to hide you root
Hell4Ge said:
I feel like I am confused with all these terms:
Rooting the device is just elevating the default permissions to root level so you can do whatever you want, just any operation is under sudo privileges.
Recovery is a "something" that handles data wiping, installing low level packages (most likely custom roms), making backups, etc. Actually Recovery is a mode / app that user can operate without having Android installed on their phone. See TWRP or CWM.
Flashing - installing firmware thingies from low level mode (recovery / adb)
Bootloader is our OS picker, for Unix-like systems its usually GRUB, but in mobile devices it does not have a name I guess
Bootloader unlock / unlocked bootloader - I don't know nothing about that, except this is prerequisite to root the device
ROM Kernel - a Unix-like OS core, having scary versioning number like 123.456.777.888.12a-dev/rc
Stock ROM - a rom full of bloatware, we don't like stock roms
When we speak about rooting device, what is actually rooted? A bootloader? a rom? a kernel?
According to this topic, the rooting method depends on used bootloader and kernel version - how does it come together? I don't think that bootloader depends on rom kernel version as bootloader will work without any OS.
A quote from the guide: "New official updates are scheduled to be released soon and the phone has to be unrooted for them to be installed." - but I am root and I want that update right now :laugh:
Click to expand...
Click to collapse
Dear friend, you CAN do it right now.
Simply use Magisk, the systemless rooting method.
It does miracles!
It does non alter the system partition, only the boot one, and give you a root that can be hidden to any app you want.
If you hide it at the update app, you will do update, so called OverTheAir, or OTA.
If something is wrong, please correct me, çause I have discovered the power of Magisk just a few days ago, and I'm still enchanted!
Magisk page is here: https://forum.xda-developers.com/apps/magisk
Love and Enjoy
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
nabril15 said:
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
Click to expand...
Click to collapse
1: yes. For anything you need root for, really.
Most bloatware can be removed without root, unless you want to start removing system apps. There are a few treble roms available over at the treble forum https://forum.xda-developers.com/project-treble.
Most, if not all, should be compatible. And you have https://openkirin.net/ which are for Huawei phones.
2. It does not. Well, it depends on where you read it. TWRP couldn't decrypt /data before, so you had to Format it and remove the encryption flag in fstab, but that is not needed anymore. (Official TWRP still can't, see download link below)
3. Do not rebrand. A09 is not compatible with L09/L29/AL and you will brick.
Also, if you had used it you would now be bootloader locked. What FH does is that it flashes an included oeminfo that has dualsim enabled. This also changes your IMEI, IMEI2 and SN in fastboot, making your old unlock code invalid. And right now there is no way to get a new one (I'm not sure if DC still works with A09, it doesn't on C432 as of B145.)
4. Yes. As ramdisk is overwritten you have to flash Magisk again (I suggest Magisk as SuperSU is not updated anymore)
Basically, you want to:
Go here to download TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or Beta Magisk, can be buggy: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Backup your sdcard contents.
Go to Settings -> System -> About Phone -> Tap Build number until Developer options is enabled
Go to Settings -> System -> Developer options
Enable OEM Unlocking
Reboot to fastboot.
Unlock bootloader using: fastboot oem unlock ##unlock_code##
Use Volume key to move to 'Yes' on phone, then power to accept.
Wait for format to finish, setup phone again.
Transfer magisk zip to sdcard.
Reboot to fastboot again
Flash TWRP using: fastboot flash recovery_ramdisk twrp_bla_alp_0.7.img
Reboot to recovery by holding Power and Volume Up.
Enter your Pin
Now flash Magisk
Finished.
ante0 said:
1: yes. For anything you need root for, really.
Finished.
Click to expand...
Click to collapse
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
nabril15 said:
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
Click to expand...
Click to collapse
1. Either you can use adb: adb reboot bootloader
Or power off phone then hold volume down and plug in usb
Or plug in usb, reboot, hold volume down.
2. Yes, it's fully functional.
3. Magisk is preferable. Mainly because it's being updated, and can pass Safetynet if any of your apps need it to pass.
4. You *should* only need to flash recovery_ramdisk (I guess you can use the one from the last update on http://pro-teammt.ru/firmware-database/?firmware_model=BLA-A09&firmware_page=0)
To get recovery_ramdisk you need to download update.zip from pro-teammt.ru, then extract update.app from it.
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Extract Huawei Update Extractor zip and run the exe. Go to settings in the program and disable header check.
Next open up update.app in it, rightclick on recovery_ramdisk and click on Extract Selected.
Now you can flash that image using fastboot (fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img)
This will restore stock recovery and will let you flash OTA directly from System Update.
The reason you have to restore stock recovery is because phone will reboot to recovery to update, but if you have TWRP flashed it won't update at all
You would have to flash back both TWRP and Magisk after update finishes.
(You can actually flash FULLOTA Update.zip directly in TWRP if you use HuRUpdater, but seeing as the US Mate 10 Pro rarely get any updates it's not really needed.)
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? What ROM are you using on this phone?
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
nabril15 said:
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
Click to expand...
Click to collapse
I do not have a US Mate 10 Pro (A09), but the global (L29) on C432.
You can read a bit in this thread about the US version updates:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
I guess the lack of updates is due to the problems Huawei has with the US government. :/
You do get updates, but there seem to be a few months between them.
I would update and then root. There is an update in that thread which is fairly new, but it has not been indexed by Firmware Finder (pro-teammt.ru). You could flash it using TWRP and HuRUpdater as I don't think you have Nocheck recovery for A09.
Important notice! : iLLNiSS made me aware of a serious risk!
If you play with the firmwares manually and not with the flash all bat then DO NOT flash the blobs!
These are the actual bootloader files and stuffing up here will cause a hard brick!
I have to stress this out as it is serious thanks to not having working APX drivers a flshing programs for the Shield!
For starters, I uploaded a copy of the 7.2 developer firmware here:
7.2 developer ZIP on Dropbox
It is the full 1.1Gb update and not the 422mb block based one.
I have done some extensive tests since the first block based update wrecked my rooted Shield.
Some of it will end up in this post as info for everyone.
But lets start with what seems to be the problem for a lot of users right now who run a rooted Shield : Fixing the problem
A downgrade is officially not supported by Nvidia but my tests showed it works just fine if you only go back to the 7.1.
So far my tests showed differen sources for a Shield no longer working after the OTA.
1. The device had an unlocked bootloader and you got the 422mb block update.
This would have stuffed your bootloader and the Shield won't go past 1/4 on the progress bar for the update.
You are in luck as just flashing the 7.1 bootloader will fix it.
After that just dismiss the update and change the settings to manual updates.https://forum.xda-developers.com/editpost.php?do=editpost&p=78466377
2. Your device was already fully rooted and you got the full update that resulted in your Shield doing all sorts of thing but nothing properly anymore.
As long as your apps are still there and the Shield is still somhow usable you are lucky again.
A downgrade to 7.1 will fix it, I will explain the steps required further down.
3. You made bid mods, used Magisk or other rooting tools and now your Shield complains that your system is corrupt.
Bad luck if your bootloader is locked as you loose it all.
Lucky if the bootloader is unlocked as you might be able to keep most if not all during the downgrade.
General words of warning:
Even if your bootloader was unlocked from day one I can not garantee that the downgrade will keep all settings, apps, databases and so on.
For me it works fine as I kept all vital databases on external storage.
The procedures are all based on the developer firmware, on the stock firmware some things can still be done but then again you should not have more than software problems.
On the stock firmware the bootloader is locked by default and you can use some things required to owngrade due to the restrictions of a stock system.
General downgrade procedure for the developer firmware to get back to 7.1 :
If the update did get stuck on the progess bar early on and a reboot won't fix it so you can dismiss the update you just follow the steps.
If you can reboot into the 7.1 then just dismiss the update.
Trust issues or curruption warnings at boot but an otherwise working shield on 7.1 require to flash the 7.1 bootloader again.
In some cases it is possible to skip the corruption warning with a connected controller.
A reboot once you got to the homescreen will determine how bad it is.
Reboot goes fine: You are good.
Reboot keeps nagging with warnings other than the unlocked bootloader: Downgrade.
The downgrade is only required if you have problems or the Shield already runs on the 7.2!
In almost all other cases just flashing the 7.1 bootloader is sufficient.
Fixing a stuffed Shield by sideloading the 7.1 firmware while keping all apps and things:
Enable USB debugging and allow the connections for the computer if you still have access to the settings.
Otherwise you need to flash the 7.1 fresh and might loose vital things that need to install again.
Reboot into the stock recovery, if you use TWRP flashed on the Shield already then please flash the recovery from the 7.1 firmware first.
Hook up the controller and pressing A or B should get you into the normal recover screen past the dead droid.
ADB sideload XXX - where the xxx stands for the filename you have for the developer ZIP.
After the rebbot you should be back on your 7.1 homescreen and can dismiss the 7.2 update.
Also change the update settings while at it
Fixing a fully stuffed Shield and then downgrading to the 7.1 firmware:
If all went down south then you tried a few things and realised there is no way to get your data back and even less to prevent the 7.2 update.
Installing the 7.1 from scratch forces the setup wizard and before you can get anywhere you need to update to 7.2
So much easier to use the linked 7.2 update from above until Nvidia provides it on their download servers.
A vital thing to do is to keep the bootloader locked!!
Same for NOT having TWRP installed on the Shield!
If in doubt flash the 7.1 boot and recovery partitions first then go back into the stock recovery and wipe the cache.
Coming from a stock developer firmware with just an unlocked bootloader you are good to go.
Sideload the 7.2 update.
Unplug when the reboot starts and go into fastboot to lock the bootloader: Fastboot oem lock.
This is a vital step as the new kernel otherwise could ruin the completion of the install.
Ignore the double hassles and go through the wizard so you can enter the settings again to enable the developer mode and USB debugging.
Unlock the bootloader so you can do it all again Last time I promise!
Once you have both the bootloader unlocked AND the Shield in a usable condition past the setup wizard:
Reboot into the recovery to sideload the 7.1 firmware.
After the next reboot you are back on the 7.1 homescreen drirectly and can dismiss the update.
Possible tricks that can help you to prevent the installation of the 7.2 update if you come from a fresh 7.1 install instead:
Don't allow the reboot and instead use ADB to reboot into the recovery.
Wipe the cache - this will remove the scripts required to start the update after the reboot.
The next reboot should bring you back to the homescreen where you can stop the new download of the update and change the update settings.
TWRP, full root and new security measures in 7.2:
The 4.9 kernel used also makes use of a Fstab configuration that no longer includes the system partition.
This and other restrictions currently make the normal use of Magisk impossible.
With no system partition available to Magisk the changes in the boot process come to a stop and the Shield gets stuck during boot.
The added restrictions also make it very, very hard to manually add SU and busybox.
At least without getting the currupt system popup on every boot and finding out that a lot of things still don't work properly.
A final 7.2 firmware is said to be available on the download servers today.
If this final is no different from the current OTA then it will not be of any use for users requiring a fully rooted devices.
With the stock recovery still using the old kernel all attempts to use recovery functions to alter the system for rooting fail as well.
Can't blame the company as all this is part of Google revamp og security and closing backdoors and loopholes for possible attackers.
Personally I think it is Googles way of keeping control over devices they don't actually own.
Anyways I did make some little progress:
Plans for the near future:
Security is good but I like to know what my Android devices are doing and especially what Google likes to collect if I can not find ways to stop it.
So I will not try to use any backdoors or secrurity vulnerablilites in the new kernel to allow a full root on my Shield.
I will go the route I know best: Manual labour
The bootloader is already fixed to allow what we are used to from previous developer firmwares.
As SU and busybox can not be manually entered at this stage I will try to include them directly in the stock 7.1 firmware while renaming the OTA updater to have it a bit easier.
Assuming that works as expected I will do the same on the 7.2 firmware and compare the corresponding scripts and so on.
If the standard SU still works on an "unlocked" 7.2 I should be able to adjust the Magisk ZIP accordingly to implement it into the bootloader.
Only need to figure out if Magisk then has enough rights to work and the system is still happy to accept the changes.
I noly have the 16Gb 2017 model to work with but since the bootloader seems to be same for all Shield models I think if it works then it should do so for all models.
In the meantime I hope the infos here will help some pople to get their shield back without the need to sent it in.
Update 25/12/18: I got TWRP working on 7.2
This is only true for the 2017 model though as I have only this for testing.
Currently creating a backup to the internal storage.
If the restore works then I will upload the new TWRP - for the said model only!
Give me a day or two to fix it for the other models too.
There is progress on the rooting front as well.
Created new scripts for my kitchen to be able to handle the new file_context thing.
A fully pre-rooted and totally unsecure (in terms of ABD, DM-verity and such) is already cooked, just did not dare yet to try it out as I have a real life job too.
As for the pre-rooted firmware:
Things have changed quite a bit with the new kernel in terms of "just adding SU or Magisk".
Magisk might see an update for this problem soon, SU however seems to tally fail on two levels.
So far I was unable to do a full install of the modded firmware.
Flashed all at once and the boot just hangs.
Bootloader, reboot, then the rest seems to work.
At least for the basic install of the system.
If I add SU and busybox the system still ends up with a corrup notice during boot and then it fails.
Tune in over the next few days for progress updates at the end of the thread.
Major developments will be added right here.
Just a matter of finding the last restrictions.
Once that is done Magisk should be possible as well.
Ok, TWRP boot fine, does a backup but fails to restore the system to a bootable state.
Will now check if at least installing a zip works.
Well, it did not, so TWRP has to wait a few more days
I edited post 3 with instructions on how to "unbrick" and go back to 7.1.
Update 27/12/18: A friend of mine found some intersting stuff.
A 7.2 firmware offering a pure Android without any TV stuff but also a full root possible.
I hope he will share his finding here soon or allow me post it all in his name.
For now lets just say: It really works if done the rght way!
Full write rights, installing Magisk modules and all.
All thanks to an undocumented flaw in the device security structures, so even without any hidden backdoors or such LOL
Update: Whiteak was so kind to provide a working root solution in post 36, please check it.
I can confirm it is working as promised.
So the credits for this one go to Whiteak and the credits for the idea and use of the DTB file to Zulu99 - great idea!
To prevent any problems I advise to perform a factory wipe after the install and before the first boot.
Switch to the stock recovery to do this then boot as normal an enjoy.
A complete firmware with the required mods is sitting on my PC just waiting for idiot behing the keyboard to figure out how to pack it properly for flashing.
Once that problem is sorted and also TWRP working again things will get a lot easier.
Annoying update:
I was not able to confirm my web findings on the 7.2 firmwares bootloader but it seems other devices running the same type of kernel and bootloader and a bit lost now.
AVB is fully implemented on the latest level.
(Again I am working on confirming or denying these findings!)
This means any alteration to vital parts of the system will fail with a corruption warning or worse.
Custom recovery access is limited if not fully restricted.
But even if it works you still need a firmware to flash that either is able to disable all this crap, hoping the bootloader alone will allow it, or
to hope Nvidia will provide a future bootloader update with these restrictions removed.
We can not downgrade the bootloader and even if there is some old one out there that would actually be flashable the risk is high to end with a brick anyway.
The DTB, at least in my tests gives us the required system wide write access but I have no information about the AVM verfified boot other than that Zulu99's firmware works.
But if it was compiled with the NVidia developer suite then it will be signed accordingly so the bootloader accepts it.
Could not find any info on how his firmware was actually created.
It gives me the hope though that once I have a fully working TWRP again that my modded 7.2 will work as expected and with no restrictions anymore.
Thanks for the info.
Edit: Will use this post to list options to recover the Shield is all seems lost.
As a result of far too much rom cooking and mods I needed a 100% working way to recover the Shield in case things turn very ugly.
So lets sum up what I define as very ugly when playing with firmwares:
1. Firmware installed but the Shield just hangs on the logo.
2. Firmware installed and now the system is corrupt and even it is boots it takes forever to get around the nag screens.
3. Firmware downgrade attempted but now the Shield won't even boot anymore.
4. Anything that would qualify for a soft brick.
My worst case when I only got a flashing white screen after trying to restore a TWRP backup under 7.2.
There any many way that work for a variety of boot problems but it takes too long to list all cases I encountered with a list of fixes that work or a comment that only the below way works.
So just to be clear here: This is not for any recovery purpose other than fixing what can't be fixed through a factory reset or fresh flashing of the firmware!
1. Get the Shield into Fastboot mode: Connect wired controller and male to male USB cable.
2. Power the Shield up while holding A and B on the controller.
Keep holding until you see the fastboot menu on the screen.
3. Install the 7.1 recovery firmware for your Shield type after unpacking it.
With Fastboot connection working type: flash-all.bat and hit enter.
4. Keep an eye on the progess!
5. Once the Shield is finnished and reboots, hold the A and B buttons on the controller again to enter fastboot mode!
Do not let the Shield boot up other than into the fastboot mode!
6. Lock the bootloader! Fastboot oem lock
Confirm with the controller, then go down and select the recovery kernel.
7. Once the dead droid is on the screen press B on the controller to enter the real recovery.
If B does not work try A
8. Select the factory reset option to wipe all!
9. Once the wipe is done you can boot into 7.1 as normal again.
10. With a bit of chance you might even get directly to the homescreen if the previous setup was completed.
If you need the full seup wizard again and are forced to update to 7.2 then at least the update will work fine this time around.
In case you desire to go back to the 7.1:
If you just finnished the above only to end with the 7.2 then set it up and flash the 7.1 - you won't get the setup wizard again and can skip the update.
If you are on a working 7.2 that was update the OTA way but want to go back:
1. Install the 7.1 firmware.
2. Lock the bootloader.
3. Boot and then skip the update to 7.2.
Any idea what to do if the Shield sticks at the NVidia logo when you select Recovery from Fastboot? I reflashed boot and got the same result.
psycho_asylum said:
Any idea what to do if the Shield sticks at the NVidia logo when you select Recovery from Fastboot? I reflashed boot and got the same result.
Click to expand...
Click to collapse
It won't work from fastboot.
Fastboot operates on a different level and calling the recovery from there lets it end up in nowhere with no access to the system.
You need to boot into recovery through ADB as (for the new model) without a power button and usable hardware buttons we can't get into it otherwise.
Having said that, the fastboot way should still work with an unmodified bootloader.
When the dead droid is on the screen the recovery should be available after pressing the A button on the wired up controller.
But during my tests on 7.2 it did not always work, so you might have to try a few times and also try the B button.
Downunder35m said:
It won't work from fastboot.
Fastboot operates on a different level and calling the recovery from there lets it end up in nowhere with no access to the system.
You need to boot into recovery through ADB as (for the new model) without a power button and usable hardware buttons we can't get into it otherwise.
Having said that, the fastboot way should still work with an unmodified bootloader.
When the dead droid is on the screen the recovery should be available after pressing the A button on the wired up controller.
But during my tests on 7.2 it did not always work, so you might have to try a few times and also try the B button.
Click to expand...
Click to collapse
I have not been able to get to the dead droid screen.
Downunder35m said:
For starters, I uploaded a copy of the 7.2 developer firmware here:
7.2 developer ZIP on Dropbox
It is the full 1.1Gb update and not the 422mb block based one.
(snip)
Click to expand...
Click to collapse
Thanks for posting this, but please note that this firmware is only for the 2017 16GB model and cannot be used with a 2015 or Pro model.
I just got a 7.2.1 update that forced me to update. Wouldn't give me an option to skip it... As soon as I turned on my Shield, it said something about the 7.2.1 update and then rebooted and installed.
I was holding off on updating too so I didn't lose root. Now I'm unrooted and am unable to get Magisk working again until I can get my hands on a 7.2.1 bootloader... Bleh.
Weird, I am not getting the 7.2.1 at all here.
And since yesterday the OTA only tries the block based but not the full image.
AthieN said:
I just got a 7.2.1 update that forced me to update. Wouldn't give me an option to skip it... As soon as I turned on my Shield, it said something about the 7.2.1 update and then rebooted and installed.
I was holding off on updating too so I didn't lose root. Now I'm unrooted and am unable to get Magisk working again until I can get my hands on a 7.2.1 bootloader... Bleh.
Click to expand...
Click to collapse
I was able to downgrade using the 7.2 image after setting up the device on 7.2.1 OTA just make sure you disable automatic updates
Thanks downunder this kind of in-depth info is always appriciated man........i like to learn these kind of things, having bits here and bits there gives a better picture of the whole, while also giving us upto date current info.
Thanks for taking the time to write this :good:
---------- Post added at 07:35 AM ---------- Previous post was at 07:27 AM ----------
Edit
Hi downunder, could you confirm i have this correctly
With no access to fastboot thus no twrp or root, are you implying, assuming your able to inject root into stock firmware, that, i'd be able to flash this stock+root rom in STOCK recovery, which i do have access to?
Edit: im under the impression that stock firmware zips are checked by stock recoveries, so modifying a stock firmware zip tends to fail this check and thus wont install/flash.......which makes me think im misunderstanding here......or just hoping im not
If so, im interested
Edit
i just read your second post which near enought answers my curiousity, so that'll teach me to read beyond the first post before asking answered questions ........even if the post excites me............ahhh, who am i kidding, ill probabably do it again........the equivelancy of a mental post boner........not controllable
Sorry for the disgusting analogy
SyberHexen said:
I was able to downgrade using the 7.2 image after setting up the device on 7.2.1 OTA just make sure you disable automatic updates
Click to expand...
Click to collapse
Did I understand it correctly? You successfully downgraded from 7.2.1 to 7.2?
ErAzOr2k said:
Did I understand it correctly? You successfully downgraded from 7.2.1 to 7.2?
Click to expand...
Click to collapse
Yes,
Just ran flash all from the bootloader. For the newly released 7.2 developer_rooted factory image.
As long as we don't jump to Android 9 we should always be able to downgrade through a full factory firmware.
Once Android 9 comes this might not work anymore due to the massive changes involved for the boot and system checks.
@banderos101: Unless you really did something bad you should always be able to enter the fastboot mode to flash a full firmware.
If I have some time after xmas I will have another look on the options of signing the zip properly or simply to fake it.
Biggest problem will be to generate the corret SHA checksums ince all is installed so I can use the same checksums in the check files.
The bootloader needs them to identify the system and vendor as genuine.
The system needs them to confirm all is actually unmodified as otherwise all fails to boot at some stage.
Modding a proper userdebug firmware is not really that hard, but converting a release version that also is a true and secure user release...
Lets just say that it won't be an easy task.
As it looks like the kernel is a keeper I might have to figure something out unless TopJohnWu won't enjoy a break after his exams and works on a way to get Magisk working with out kernel.
At least I figured out why the recovery trick isn't working for me.
The system partition is not mounted for the sideload mode.
To apply an update the stuff is written directly onto the partition, so no file level access left to play with and break things
In comparison you could say the shield is now like a modern car with keyless operation only.
You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door
SyberHexen said:
Yes,
Just ran flash all from the bootloader. For the newly released 7.2 developer_rooted factory image.
Click to expand...
Click to collapse
Just wondering what is achieved by going back to 7.2?
What do you mean "going back"?
Right now the 7.2 is the official and latest firmware.
I was unable to get my hands in the 7.2.1 but guess it might have been a testversion for certain models only.
I wasted a few hours trying to fix the system image.
First stage was only to get the basic "features" back, like full ADB support, enabling the support to use SU and busybox....
Just what is required to actually allow these nice apps we like to gain root to work.
This backfired badly as right after the start the bootloader complained about the system being corrup and no override to get past this worked.
So of course I then removed the known restrictions from the bootloader...
As you guessed it the damn thing then did not even boot at all, just jumped right into the (locked) recovery mode.
A half decent comparision with my last manual root on a tv box that was a success showed I still did the right things...
If anyone wondered why we needed a new bootloader for the support of smart helpers an some codes stuff:
We didn't as all this could have been done with the 7.1 bootloader as well.
Since my root attempts so far all ended either in disaster or in a root access that failed shortly after/corrupted the system, I took a look of the general kernel changes that were published for other devices.
Before I could find anything meaningful I realised the 4.9 kernel is actually a requirement for Android Pie!
With that info sorted I started digging inti the new "security" features Pie can offer.
I will try to keep it simple and to the stuff that actually concerns us for rooting purposes:
The new boot process with Pie is aimed at being secure from the hardware level up and all the way into the system partion once the boot is completed.
So the hardware checks if the bootloader is actually usable - we had that for a long time, nothing new.
Once the bootloader starts and reaches the point of actually getting somewhere, all partitions required will be checks by either a hash check or a trusted certificate gererated at boot time that is compared to the previous certificate.
Only if that is fine the bootloader will call upon the system and vendor partitions.
The handover of control from bootloader to the system is made far more secure as well.
SELinux is called early on to ensure that only trusted apps and tasks can work but also to all a new control level.
System related apps no longer run as root or with special permissions.
Instead every single app and service runs as its own user!
And under SELinux conditions this means nothing can access anything that it is not entitled to unless included as a user for the other app.
And with that sorted the vendor stuff is called to ensure all hardware and vendor related stuff is still genuine - this include the required certs but also the recovery and bootloader hash codes and certs.
So if something is fishy either SELinux will stop us or the vendor stuff will just overwrite it all.
Once we finally reach the system stage the recovery is checked if called from within the system, if fully implemented it could mean that using an official update on a modded firmware will delete all data as the encryption from the old system is declared invalid.
Sadly it does not stop there because even with full rigths (faked or otherwise) to access the system partition with write access we still can not just change things.
If something belongs to a user (a secure app) than a change will corrupt the system.
To overcome all this without using vulnerabilities that so far no one has found, a compatible userdebug release has to be created from the official user firmware.
DM-Verity needs to be disabled as well as all partition encryption stuff.
The bootloader needs to be adjusted to reflect these changes and the required turst certificates generated and included in both system and boot images.
The only problem here is that the kernel won't allow these changes unless it itself is a userdebug kernel.
After that it is only the little efford to go through about 60 different scripts to remove or redirect the calls for all boot and system security related things.
If then by some chance all this actually boots up and goes all the way into a usable homescreen the entire stuff needs to be secured again.
This time so that the final system has a correct cert and checksum that matches those we need to include in the bootloader.
Anyone knows how to gain full access to the trusted keystore on the 4.9 kernel? LOL
For the moment I don't really care about all the stuff above.
I would be happy to figue out what to make out of these new fstab configurations without the vital partitions listed.
The real aprtitions used have not changed but it is impossible include them in the fastab, doing so causes the bootloader to fail.
Presumably because the kernel realised we try to get around the verification process.
This and some other minor things are also the reason TWRP fails so badly, same for the stock recovery by the way.
Since TWRP is toy a lot us like:
TWRP and 7.2....
Without a system partion in the bootloader fastab TWRP can not mount it.
Same for all other things TWRP needs to mount as it simply does not have the right to access these areas.
To make things worse, we need system access to even start TWRP through fastboot.
So, now matter if we flash or start it through fastboot: The bootloader and system will realise our recovery does not match the checksum.
What does al this now mean in terms a lot more people are able to understand?
Let me try...
Imagine the 7.2 in a running version would be just some encrypted file with a lot of folders in it.
And like PGP or other encryptions software we know there is a private and a public key.
With the public key you can see a lot and use most the encrypted file - but only to a level that is required, nothing above your low level clearance.
For every attempt to write into this file or to make changes we need the private key.
If you follow so far then lets just say the recovery (stock) and Fastboot can be, to some extent, used for this access.
But since every folder in the encrypted file also uses private and public keys it is like tracing a tree.
Although it is getting too long, let me give you the example of just adding SU to the sytem partition:
Adding SU into the system image is no big deal.
Singing this image to get a usable key and including this key into the keystore is.
Assume we would just be able to do it....
SU needs to be called quite early in the boot process.
It then elevates the access level for certain things and also intercepts all root related requests from apps and services.
Except of course those that already had these rights by default.
Problem here is that adding the scripts we need plus changing some others means violating the tree of trust on the device and we get locked out.
Finding a spot to add the required rights for SU might be still possible.
On the other hand it will be impossible to give SU any rights or access to "trusted user" owned parts, files, folders, partitions....
The entire concept of SU just fails.
I will have to check how much of the new features are active in the 7.2 kernel that hinder us.
If I find enough it might be possible it enough to call for a Magisk update.
But I guess it is of little use for just one set of devices, so maybe once more devices on the 4.9 kernel fail to work with Magisk it will be easier to spot a usable pattern.
In case someone else if already working ona mdified system: Please let me know how you made it boot after the changes
Shield Tv 16 2017 - OTA update 7.2.1 Ready for updating
Im on 7.1. I have been waiting for 7.2 developer image, which is now out and just noticed 7.2.1 is available OTA. I'm really confused what to do. I want to keep root without bricking my Shield. Should I Stay with what I have as it is running well.
I am not even sure if it is safe trying to update to dev 7.2 image (or if I would want to) by hooking to computer and using ADB Fastboot tools.
Is there any good reason to update to 7.2 or 7.21? and if so how would I go about doing it? Which program is good for flashing developer images or OTA updates. I used to use flash-fire, which seems to be obsolete now and have heard TWRP is incompatible rooting with SU with OREO updates????
Should I play it safe and stay with what I have rather than experiment and end up with a brick? (wouldn't be the first time)
Anyone know if 7.21 is some-kind of bug fix?
Alot of questions but hope someone has some answers.
Thanks for any info.
"You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door "
My fastboot issue
Yeah, i think i busted the microusb somehow with a faulty usb hub, whenever i plug the usb to my raspberrypi/windows box(for adb/fastboot) now, it turns off all usb ports on the pi aswell as the windows box, even when the shield is unplugged, some sort of earth problem maybe
......all i have is adb over network, adb reboot bootloader simply reboots back to system, adb reboot recovery works though.
ive read that fastboot over tcp(ethernet) had been introduced a couple of android versions ago, but i dont think its been implemented in our shields
infact heres a link
https://www.androidpolice.com/2016/...-capabilities-wireless-flashing-isnt-far-off/
Looks like it needs to be specifically added onto a build
As far as you making a stock root build, if you can, that would awesome, more then awesome, but if it becomes more work then you thought dont worry about it, its not like their making it easy
Also, sounds like 4.9/future android is gonna be a nightmare for root......... having the ability to root so that the option is there to see whats going on in the background of these devices, these devices posessing cameras/microphones/old+latest sensors/personal files/personal info, which reside on our personal beings or in our homes........is just one reason why i dont want to see root go away
So what is the purpose of the developer image of 7.2?
Rather, I know the stated purpose of the developer image, but if it is locked in the way described it sounds like the benefit is negated for typical developers.
(e.g. sometimes I debug an application without permissions in order to benchmark or debug a problem).
For casual users of the shield, using ad blockers and whatnot, is there any benefit to derive from installing the developer rom over stock? Does "adb root" still work?
What is left as the difference. It doesn't sound like they produced a userdebug build of the OS.
Thanks
The 2 new updates are horrible. I have gone back to 7.1. They have crippled my shield. I'll wait for a new update.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
lifebringer123 said:
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
Click to expand...
Click to collapse
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
towardsdawn said:
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
Click to expand...
Click to collapse
OK, thank you! I will give it a try eventually...
Any recommended ROMS that are lightweight but super stable and also regularly updated? Like LineageOS (which I believe is not updated for this phone)...
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
towardsdawn said:
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
Click to expand...
Click to collapse
thanks!
Ytube21 said:
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
Click to expand...
Click to collapse
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
lifebringer123 said:
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
Click to expand...
Click to collapse
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Aselloph said:
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Click to expand...
Click to collapse
The OS notices the OTA updates, but it cannot apply/install them no matter what I do to try.
Aselloph said:
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Click to expand...
Click to collapse
Makes sense; thanks.
Aselloph said:
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
Click to expand...
Click to collapse
That is correct; I don't have that option. I also no longer have the "T-Mobile" Splash sceen on startup, my assumption since doing this earlier this year was that I may have wiped the t-mobile branded ROM variant, and the phone reverted to the "slot B" stock variant. But I could be wrong. In any case...
Aselloph said:
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Click to expand...
Click to collapse
Model DE2118
Build 11.0.1.9.DE18CB
ONE PLUS Nord N200 5G
(dre8t, but unlocked bootloader via unlock_code.bin)
I would give that a whirl if you could point me to the current OTA update .zip package. However, I bookmarked that TWRP thread months ago, but it still hasn't been updated, and I never did get it working correctly. But I'll try it. If it works and the manual OTA update .zip is only monthly/quarterly, the inconvenience is not severe. Still, I'm not using root or any custom ROM at the moment, so I should really go back to a locked bootloader so I can receive OTA updates, and suck up the loss of a few hours of restoring settings/apps...
Again (for all on thread), if there is a solid Custom ROM which regularly gets security updates, please point me to that thread/ROM! The
Thank you so much for your time!
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
justauserthatusesaphone said:
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
Click to expand...
Click to collapse
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
lifebringer123 said:
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
Click to expand...
Click to collapse
you're welcome, sorry for being late lol
after 2-3 years, ill probably keep this phone and install lineageos or pixel experience (that is, if it gets support)
although by that time, the trade in value is probably 2 dollars so I'll use it if i ever get into android development.
Any word on custom ROMs for this like Lineage OS or Pixel Experience?