Related
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
packydavis said:
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
Click to expand...
Click to collapse
There are plenty of tutorials for making your own rom and kerenel. There are plenty in xda university and an excellent one by my colleague jackeagle, if you want something device specific then it maybe better to add the phone title in your op rather than just adding a tag
Regards
Sawdoctor
LG Aristo
No ROMs, no real mods and the only progress we have towards a kernel is KyleBryant's work delivering us the kernel source itself.
JustLee said:
Dang Any tips for editing the power button on the back of the phone
Click to expand...
Click to collapse
What do you mean by editing the power button? Like how it functions or it's response upon being held down?
Substratum
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
mustangtim49 said:
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
Click to expand...
Click to collapse
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
MODS
Changed BootAnimation .zip to Cyanogenmod version
Added Viper4Divine FX + DivineEQ + Dolby Atmos
Apps Added into system:
AdAway
Camera FV-5
ES File Explorer
EvolveSMS
FlySo
GhostKik
Instagram
Kik
NovaLauncher
PowerManager
Pulsar+
Removed from system:
All LG Home Apps (FIRST replace with Launcher of your choice E.G. Nova or ADW)
Lookout
All Google but Play Store, Play Services, Play Games, Gmail, YouTube, Maps, and Drive.
All LG apps but SmartWorld (yes including Messaging)
And removed more but they were minor and cant remember...
DivineEQ is blank when loaded so far.
ES File Explorer clears its "history" every time i exit the app. But major settings stick.
I know its nothing major. If I knew Android Developing, I would create a custom rom.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
xtremelora said:
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Click to expand...
Click to collapse
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
ninjasinabag said:
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
Click to expand...
Click to collapse
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
xtremelora said:
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
Click to expand...
Click to collapse
Ooh sh#t, my bad homie.
Well now that I've made a fool of myself, I'mma back up and give this a test.
ninjasinabag said:
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
Click to expand...
Click to collapse
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
mustangtim49 said:
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
Click to expand...
Click to collapse
Yeah, I already had that panned out. My comment was a simple heads up about one of the possibilities.
snafu
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
₥ike_grips said:
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
Click to expand...
Click to collapse
You're using the wrong recovery if it's still showing the ms550.
Drivers are universal inside of company devices. (LG for LG, Samsung for Samsung) so they don't conflict.
Adb and fastboot are both universal drivers and shouldn't matter for your device. (I'm using the same fastboot I installed for my Galaxy note 4 that I am for my aristo, my V10, my htc desire 610, and my uncle's v20)
Just do what you said and start fresh.
Unlock the bootloader.
Install the proper twrp and remove encryption.
Flash the stock boot partition and wipe data (this is sneakily pertinent if you're gonna use magisk)
Do not install system mods before using magisk.
After that, use twrp's file explorer to remove and stock apps that you won't need.
I bought a LG V10 today i dont know if its used or new (LOL) any way to find that out i checked IMEI says its orignal talked to people at LG USA they said its Original Here are my questions:
1) How to know if your phone is Legit like New + Lasting?( in my country they replicate used to orignal or fake to orignal)
2) How to Root LG V10? (i tried it with other phones i broke them)
3) Suggest Some Recommended Apps and ROMS?
4)I have seen a youtube video of xdadevelopers they were talking how you can overclock or under clock your device can i do that with my phone?
5)Last Question How can i myself from the infamous Bootloop? (Any Suggestion, Tricks Ways)
I am new here i need your help for not doing a rookie mistake....
1) Get the LG Phone Info app on the Google Play Market and as long as that shows "OK" in the Original info (the first box after you click the Get Information button) then your device is an original and not something that's been modified on a firmware level.
2) If you have Lollipop or Marshmallow rooting is fairly easy by comparison to Nougat. If you have Nougat on it already things are basically a stop - there is no working root for Nougat at this moment IF the device has been upgraded to Nougat using T-Mobile's OTA direct from them. Once that's been installed there's no turning back and no working root at this point but some devs are working on it, no guarantees they'll ever be able to create one.
If the device has Lollipop or Marshmallow on it you can get it rooted. The best course of action is to go from Lollipop to Marshmallow (the last Marshmallow build is 20l and that's an "L" there, lowercase, not 1 or i/I) and then what you'll need to do is get TWRP on it (that step is critical) then you would flash this modified update.zip to get to Nougat build 30b on it. runningak3d modified that update.zip file so it does NOT overwrite the recovery partition and you get to keep TWRP installed for flashing purposes. If you use T-Mobile's official OTA update.zip you'll be stuck, not able to flash anything including TWRP, or get rooted, etc.
So, again, the process is get to Marshmallow 20l, then get TWRP installed - at that point root is not necessary just to get the modified 20b update.zip on it. Then use TWRP to flash that modified 20b update.zip at which point it'll be Nougat, and THEN you can flash SuperSU with TWRP and you end up with a V10 running Nougat and rooted, that's the only method at this point.
runningak3d said he (or she, sorry, I just don't know) would try to create another modified update.zip which is pre-rooted so when installed you've got root/SuperSU ready to go but it's barely a minute to install SuperSU manually after flashing that modified 20b update.zip so it's not really a big issue there.
3) There are no custom ROMs for the V10 at this point, no Lineage, no AOSP, nothing really. There are some modified stock ROMs iirc but nothing that's totally custom and we V10 owners are still hoping some dev will take some time and create an unofficial Lineage build for the V10 based on Nougat (or even Marshmallow, I don't really care which Android version it's based on just that it's Lineage through and through). It seems pretty screwy that nobody seems to care about the V10 enough to have created a custom ROM but that's how it goes sometimes. The V10 is like an LG G4 on steroids in some respects, basically the same hardware overall with some minor differences (the second screen, of course, but I don't even use that on mine so I don't care about it at all).
I just wanted Lineage because it's so lean and efficient compared to any stock ROM and of course the potential for having a custom kernel with more governor support and other aspects is the big draw for me so, the hope remains that someone out there will take some pity on us woeful V10 owners and drop a Lineage build someday.
As for apps, well, that's entirely up to you and what you use your V10 for, and since nobody knows that but you then it'll be up to you to decide what kinds of apps you're going to be looking for.
4) Over-and-underclocking requires a custom kernel that allows for such things, and the stock kernel that's available (I think there was one custom kernel but it's just a modified stock one with limited additional capabilities) simply doesn't allow for such alterations. The V10 is quite fast on its own natively so, I can't imagine why someone would need to overclock it - I can understand WHY someone would WANT to do it, of course, but as for an actual need to do it, nope.
As for underclocking, that would save battery and be what I'd call a need in some respects, but again there just doesn't seem to be any developer out there that gives a damn about the V10 sadly. I wish I had spent more time learning how to create custom ROMs over the years and trick out some kernels as well using the provided source from manufacturers of these smartphones but I never did.
5) There is no way to prevent the potential bootloop issue which affects the G3/G4/G5/G6 (I saw one report so it could be bogus for the G6) and also the V10/V20 (seen two reports for the V20) and the Nexus 5x because it's a hardware manufacturing defect related to how the Snapdragon SoCs are mounted on the motherboards. There's nothing that you can do about it and there's no way to know for sure if the V10 you have will develop problems because of it or not, all you can do is use it and be done with it and hope for the best. Again, there is no fix and there's no way to know or prevent it from happening so, no matter what so called "fix" you read about or see a video about, it's all BS and best avoided.
My recommendation: since you just got the V10, go to LG's website and register the V10 in your name (might have to create an account) and then say you bought it in March, April, or May of 2017 (just a few months ago) and that will give you warranty protection through at least mid-2018. If you do that and it does bootloop on you, LG will replace it through the warranty period. Don't register it and you're out of luck if it does bootloop on you.
Hope this helps...
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.
Hello Guys,
I just bought a new Wemax One Pro (Xiaomi) laser projector.
I'm very happy with my purchase, picture and sound quality,....
BUT, it has a few drawbacks too, Chinese Menu's, no Google Play-store, no YouTube.
Hence I would like to root this device, I already found a user guide on how to do this in another section of this forum.
I'm posting this question here, because I think it's more appropriate.
Now for my question,... I can follow this user guide upon the letter,... BUT then I don't learn anything, and also I like to know what I'm doing.
I'm a COMPLETE NEWBIE, so I like to know what is the relation between twrp and magisc, why do I need both, and what is a custom rom.
Already have read many topics and this is what I know so far,...
Magisc is never version of supersu, superuser, with the advantage that is doesn't actually changes the system files, instead puts them save in boot.
With twrp I can get access into the recovery mode, and modify system files,... please do correct me if I'm wrong!
What I don't understand is what is the relation between these two and why do I need them both?
And what is a custom made rom, does this alter system files?
Maybe you guys know a link to a good beginners guide, external or on this forum.
Or just maybe someone can explain this to me very briefly, I don't want to become a wizard of developer, I just want to understand what I do.
Many THANKS for all your help, and replies !
A very short answer, sorry for this
A custom ROM is a 3rd-party firmware for Android devices in contrast to device's built-in stock ROM
TWRP is a fully touch-based custom recovery used on phones to carry out a host of major hacks and tweaks, from creating full backups to flashing custom ROMs. Android offers only a limited stock recovery function. Without a custom recovery you won’t be able to flash a custom ROM. Note: Device must not be rooted. You install TWRP typically by means of its installer or by means of Fastboot *).
Installing SuperSU or Magisk into your Android system means you are rooting the Android system. The rooting process differs from device to device which makes it impossible to give general instructions on rooting here. All you need is an unlocked bootloader in your device !! When confronted with Android rooting, you often have to work with Fastboot *).
*) Fastboot is part of Google’s Android SDK and is mostly used to re-flash partitions on your Android device, similar to (custom) recovery mode. Rooting is done using custom recovery these days!
Thanks for your reply!!
So does this mean I can change the system language from Chinese to English just by applying a custom ROM?
And would I then also be able to remove bloatware?
One last one, sorry for this.
Is it true I can't install customs ROM's without rooting my device?
GI30065 said:
Thanks for your reply!!
So does this mean I can change the system language from Chinese to English just by applying a custom ROM?
And would I then also be able to remove bloatware?
One last one, sorry for this.
Is it true I can't install customs ROM's without rooting my device?
Click to expand...
Click to collapse
A1: Changing Android's system language is achieved via Android's Settings, look here.
A2: Removing bloatware has be manually done, one by one, by you: bloatware isn't part of any ROM.
A3: Have already answered this question in my previous post.
Wondering if anyone is thinking of developing custom ROMs for this device. I see that the kernel sources were released and the bootloader is of course unlockable.
Not a dev, but if you look at the entire moto g line and even budget motorola phones in general, most of these devices have at least a few custom rom options. i went from the moto e4 to the moto g5s plus to the moto g6 to the moto z3 play to this and all of those phones had multiple custom rom options. This device has great potential, im sure it will pique the intrest of at least a few devs.
testtubebaby said:
Wondering if anyone is thinking of developing custom ROMs for this device. I see that the kernel sources were released and the bootloader is of course unlockable.
Click to expand...
Click to collapse
Started trees for it and have OmniROM running on it. Sadly, cause of corona, i'm not at home and i don't have the phone with me, so can go further for now.
Trees are available at boulzordev org on GitHub.
I got the stylus instead of this device but it already appears as though this is the one getting more attention
Sent from my [device_name] using XDA-Developers Legacy app
I couldn't get Lineage 17.1 to build on my pixel 3a without errors but I can try using the G power blobs I found online here. My G power is not rooted so I did not obtain them myself so anything goes. I'm not rushing on this due to kids/work/etc.
One thing I think would be of value is a kernel with Kcal. Total control over RGB colors and Saturation. My last phone was LCD and with Kcal baked into the kernel and using Color Calibration app or Kernel Adiutor, cranking up the saturation really made a difference. Bland orange color went to vibrant red. I don't care about all the other tweeks to use AKT rpofiles etc. I just want more control over the screen. Keep it simple for less hassle.
Since we can't install a custom recovery, we have whatever magisc modules work, whatever exposed works, and a custom kernel. I think the stock ROM is ok as is. Just wish I could control the color more.
And of course we have to hope the custom launchers can catch up with gestures.
Working on getting TWRP to work. Basically repacking the kernel with a version of twrp thats already built. I was able to boot twrp for the moto g power and get adb up and running, but it dies before twrp is actually fully up and running, so the twrp adb commands don't work.
I used the G7 power image they had on that try. Going to try the Moto One Power next. If that doesn't work I'll just build it eventually. Unless they get to it first.
CodyF86 said:
Working on getting TWRP to work. Basically repacking the kernel with a version of twrp thats already built. I was able to boot twrp for the moto g power and get adb up and running, but it dies before twrp is actually fully up and running, so the twrp adb commands don't work.
I used the G7 power image they had on that try. Going to try the Moto One Power next. If that doesn't work I'll just build it eventually. Unless they get to it first.
Click to expand...
Click to collapse
Have you tried contacting TWRP? From their website: "If you are a company interested in a partnership or a developer who is interested in porting or working on TWRP, you are the 1% who will likely get a reply. Thanks for your consideration."
Heh I just got TWRP to boot with the GUI up just repacking the moto one power twrp, but there was no touch screen control and it could only see the external sd. Instead of hacking it together I found a dummy device tree from androidblobs, so I forked it and will just build it.
I don't have the build system on this computer anymore so ill start downloading that will take a bit and ill have to mess with it a bit, but its a start.
Basically if you can get it built and working then you send it to them and they try to build it and then theyll post it as an official supported device. I'll work on it.
https://github.com/codyf86/device_motorola_sofia
androiddiego said:
One thing I think would be of value is a kernel with Kcal. Total control over RGB colors and Saturation. My last phone was LCD and with Kcal baked into the kernel and using Color Calibration app or Kernel Adiutor, cranking up the saturation really made a difference. Bland orange color went to vibrant red. I don't care about all the other tweeks to use AKT rpofiles etc. I just want more control over the screen. Keep it simple for less hassle.
Since we can't install a custom recovery, we have whatever magisc modules work, whatever exposed works, and a custom kernel. I think the stock ROM is ok as is. Just wish I could control the color more.
And of course we have to hope the custom launchers can catch up with gestures.
Click to expand...
Click to collapse
Just read a thread here that TWRP for "sofia" is coming right along... can't wait!
has anyone tried any treble ROMs at all?
I'll be a dev