Related
I have solved this problem I think last night by updating to XXEMB1 on Kies last night - I have of course lost root for the moment but will get back to that later when I have more time
I have an international galaxy gt19300
It had begun to restart itself a few times a day and then would run for days with no issues
I eventually decided to root it when I found the new toolkit on here which seemed to work a treat
I now had superuser installaed titanium back up and ROM Toolboxand paid for pro versions of this and toolkit
to be honest apart from doing one back up using the toolkit the only other thing I did was to disable the auto scanning on start up to speed up booting the phone. A day or two after this the problems started again but this time with it no rebooting but just freezing. Eventually I took out the sd card as I remembered I had an sd card problem with my old S2 - though this is a new samsung sd card. At first I thought that was it but then a bit later it froze while i was browsing the app store and has done so periodically, though today it ran all day without freezing onvce. Then suddenly it froze again for no reason - I was just swithcing screens and it froze part way through the process
As far as I can see I have three options
1) Flash a new ROM (for the moment I am still using the stock rom having only just rooted it using Toolkit.exe from here) but not sure which one I should use so need reccommendations
2) Use the toolkit to download a stock odin flashable rom (but dont I have this already?) and then 3 reset the flash counter using triangle away (seems risky to me) install the stock rom , undo root (if necessary) and then return the phone to Samsung
3) go to Kies and install the latest update in the hope that the problem will go away - though if S User pro doesnt manage to keep root I wiill presumably have to re-root all over again.
What attracted me to S3 Toolkit was that it packaged up all sorts of options into one easy package - on the other hand this may have made me a little over confident with rooting. If I hadnt rooted it the earlier problem, though not as bad, would still have been there but I could easily have sent it back to Amazon UK or Samsung UK for repair and replacement.
My biggest worry at the moment is that whichever process I go for - or even a third option suggested here - there must be a risk that the phone might lock up during flashing or upgrade - probably not likely as it didnt when I restored the back up I had done (didnt help either) and the touch wiz ui wont be running
Anyway would really appreciate some help guys - even if it is only what you would do in the same circumstances. I guess I should have tried to have the problem fixed but earlier I put that down to maybe having too many apps and crapware and thougth rooting would help me solve it. I have unintstalled every app that I dont regularly use but it is still happening
gbswales said:
...
Click to expand...
Click to collapse
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Thanks for your advice
chrismast said:
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Click to expand...
Click to collapse
Firstly the good news is that it turned out to be a problem with the last XXELLA upgrade - I found a new one on KIES ran the update and it is fine
Of course I lost root access but expected that anyway.
I do enjoy tinkering with Systems and although I know my way around Windows I have not tried with Android until now - this is my second Galaxy so was naturally wary of bricking it if I rooted. Christmas time I bought myself a galaxy tab 2 10.1 with the express aim of rooting it and was prepared to take the risk - after a few false starts I got it rooted fine - was still wary of the phone but once the kit came out the benefit that has for me is the way you have to check things step by step systematically as you do things - my problem with doing stuff from instructions on line is that I find it is all to easy to skip a step (which I did with the tab first time around) Also with it being a system I haven't explored before I like having a step by step approach which is the same way that I learned DOS way back in time.
I do want to try some different ROMs on it to see what they offer and I would really have liked to have got some apps running from my external SD card and I also like having a complete image back up (as I have for Windows 8) so that in the event of a serious issue it is easy to wipe all and restore from new (I keep several images which I make on a weekly basis so that I don't have to re-install everything.
I confess to playing with computers and devices as a hobby - evidence of this was the 350 apps I had installed before I started purging them in case that was the cause of the problem. I pretty nearly try every new app I find just to see what it does and so there being a whole range of apps that I couldn't install without root access upset me. I am not going to rush to root again and will at least wait until the current version has been on the phone a while - just to make sure the XXEMB1 version is stable now - it has a lot of new admin features to keep me amused for a while!
Two things that disappointed me about root were that it looked as if I couldn't overclock the device to improve speed - the main CPU bar was already on max (though I didn't have time to explore more than that) and that it still seemed pretty hard , if possible at all on the hardware, to run apps from the external SD card -- as I do now with windows (using a smaller SSD ) I will have to be a bit more prudent about uninstalling the apps I find I don't really use.
I guess deep down the main reason why I want root is I don't like any manufacturer telling me what I can and cannot do with the device I paid for - one thing I did try was installing Linux but that didn't quite get finished before I lost root access.
Your advice however is very sound for people who don't like or enjoy tinkering or taking risks and I don't think I would recommend any normal phone user to root their device.
Thanks again
Just to add quickly....to overclock you need to flash a kernel that supports it.....And know what you are doing before doing it
Hi all,
Putting it briefly....
Factory reset of hdx 7" on 4.5.2
Stuck at Kindle Fire logo
Shows in PC as Internal Storage but just empty folders Music, DCIM etc...
Can get ADB connection (good news?)
That's it....now here's the interesting bit.....
If I use Kindle Fire Utility and try to root using Towelroot the device goes straight go lock screen. I slide to open and am confronted with Towelroot app. Click on Make It Rain but nothing happens.
If I try other things like installing SU it returns with permission errors.
I can also get to the devices settings too. No other apps installed just HDXPOSED and TOWELROOT.
Got me baffled... Any ideas how to fix?
You can NOT use Towelroot for 4.5.2! You must use Kingroot. Read about this, I've no experience with it. From what I've read it's possible it requires internet connection, I also read this could be for optional download of some browser or whatever, so try to disable such options, if available. You should avoid internet connection, or have it as short as possible, to avoid OTA upate from Amazon to 4.5.4.
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
myotai said:
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
Click to expand...
Click to collapse
Nothing comes to mind. Generally being stuck at the grey Kindle logo is terminal on a device with stock recovery and a locked bootloader. For future reference HDXPOSED is obsolete and may have contributed to your woes. It was never designed for FireOS v4 and doesn't work well on later versions of FireOS v3.
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
myotai said:
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
Click to expand...
Click to collapse
Assume you tried another factory reset. Being stuck at the orange logo offers some hope but there is no Rx that I know of.
Obtaining root is obviously desirable. You can try installing Kingroot via adb install and hope it executes (like towelroot apparently does) and continues to completion. If successfully you could try to repair the damage that is preventing FireOS from fully booting.
I recall someone saying installing a different launcher (eg: Nova) allowed their Kindle to boot.
Another path is to place the 3.2.8 rollback file into the root of sdcard and hope it takes.
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
myotai said:
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
Click to expand...
Click to collapse
You probably won't find that (not aware of any forum postings). Here's the deal. You are operating in uncharted waters trying to revive an unlocked/unrooted device that got borked for unknown reasons. You are going to have to a bunch of research and take some chances. FireOS can be a bxxch to repair. If the device is under warranty your best course of action is to engage Amazon for an exchange.
Kingroot is a longshot idea which I would not have mentioned if not for your experience with Towelroot. I have no idea if it will work.
Google (or another search engine) is your friend. A couple representative links below that popped up on the first attempt. I have no experience with either site an can not vouch for the content. Just a starting point ...
- Kingroot
- ADB Info
Thanks for your feedback!
I guess nothing ventured n all that!
Its a paper-weight at the moment so can't get much worse.....I'll wander around those un-charted lands and see what I come up with!
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
So you're on 4.5.2 rooted & OTA disabled now? Then try to install Safestrap v4. If it works, backup your stock slot (even if it doesn't work, who knows what it'll be good for), and move it to your PC. As the secondary slots won't work with WLAN atm anyway, you can install one of the Safestrap v4 compatible ROMs, e.g. Nexus, or CM11 in the stock slot, don't create any secondary Slots (yet).
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
To confirm you are now on rooted 4.5.2 but can get beyond the FireOS settings menu. If you install an apk via adb can you retain enough control to launch the app UI? You can do this via an adb shell command; unfortunately, the specifics are beyond my knowledge. Hopefully someone else can jump in or you can research on your own (if needed).
There is no safe way to repair FireOS directly with a locked bootloader. On many Android devices you would simply reflash/reinstall the ROM. Unfortunately, Amazon neutered the stock recovery environment as you discovered. If something goes wrong you are in a world of hurt. I think there is a very good chance your device can be revived. Just need to proceed carefully and not bork things to the point were you don't get past the grey logo. That generally means you own a door stop.
Thoughts (sorry if these are obvious):
- Keep in mind OTA is probably enabled on your device. Stay off wifi if you get that far; best to use a tether for file transfer, etc. until the problem is fixed. You can also rename the OTA apk via adb ... but your focus should be elsewhere at this point.
- It appears the FireOS launcher is hanging during initial setup (as you did a factory reset). You may find joy by installing another launcher (eg: Nova via adb) which often set themselves as the default when installed. Once you regain some control you can then install Safestrap v4 which is the pathway to other roms or repairing 4.5.2. Be aware FireOS will try to reset the default launcher on reboot. If this method works don't mess around trying to fix stuff. Install Safestrap v4 immediately (you also need to open the app and install Safestrap recovery) so you retain some control over your device during further troubleshooting.
- If a different launcher does not work try going for Safestrap v4. You will probably need to get smart around adb shell commands as you have to launch the UI to install the Safestrap recovery environment.
Thanks all taken in - my knowledge of ADB and its various commands are being added to as the hours go by - never really used it before.
Determind though........!
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
myotai said:
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
Click to expand...
Click to collapse
Yep - just flash 4.5.2 rom from here (don't use any other - you'll be rewarded with a brick). I strongly suggest you backup your existing stock slot (containing CM11) and reflash that to a secondary slot that you'll need to create. You won't be able to use wifi on the secondary slot but it will give you a rom to boot into in the event something goes wrong with the FireOS flash. Once you get FireOS working in the stock slot you should be able uninstall Safestrap. The operative word is 'should' as the system and recovery partitions need to be consistent for FireOS to boot properly. From what you have shared there is no reason to believe this is not the case - but the risk can not be dismissed. The other option is to leave Safestrap installed which only adds an annoying splash screen on boot but otherwise does not impact performance. What it does do is give you a pseudo-recovery environment which can be quite handy as you have discovered! It's also the vehicle for installing other roms such as CM11, Nexus v4, etc.
Take note of the cautions in the linked OP, in particular OTA. After flashing 4.5.2 you'll need to root and rename the OTA apk before enabling wifi. Amazon is aggressively pushing 4.5.4 which can not be rooted. Don't ruin your day - block OTA (yea - that was stupid).
Thanks so much. Its worth listing the procedures that got me this far...
I think installing TOWELROOT via ADB despite the fact I knew it wouldn't work was oddly the only thing that got me as far as 'settings' from a stuck Kindle logo. Then I had to resgiter the device in order to go to 'new offers' in the books setting to access the browser.....emails......Kingroot......finally Safestrap....boom!
I recently managed to snag one of these up at a local walmart recently (well, 2 actually) - So I would share my experience with the software aspects I have dealt with so far.
Upon opening the box, I removed the NanoSIM (before even powering it up) and gave the device a full charge - no setup yet or anything.
I then went through the initial setup, skipping everything - not signing into Wi-Fi, or added my google account. The system was on B130 or B140, I can't recall now. I enabled developer settings, enable usb debug and checked OEM Unlock (for bootloader). I then connected it to my PC (I already had the proper drivers installed, and Minimal ADB and Fastboot) and proceeded to unlock the bootloader via the official code from Huawei. This of course gives you the warning that the phone is not secure, every time you power up the phone from fully off (or restart)
Now that the bootloader was successfully unlocked, I installed TWRP from the thread "[TWRP]Unofficial[5/21/2017]huawei ascend xt" by madvane20 using Fastboot. This was perfectly successful. Upon first load of TWRP I swiped to allow modifications.
Once in TWRP I copied the B180_Full_Update.zip from "[Guide]Huawei Ascend XT - How to update from any version up to B180 after rooting" by clsA - to a 4GB MicroSD Card that I put in the phone. I mounted system and cust, as it instructs in the thread - then proceeded to do a factory reset, format data from within TWRP (I might have done an advanced wipe too, and checked everything but the external SD, but I can't quite recall) and then did a reboot directly back to recovery.
I then proceeded to make sure that system and cust was mounted again, and installed the B180_Full_Update.zip - wiping dalvik/cache after. Then I did a standard reboot system, but the phone failed to boot. It just stopped at the unsecure warning, where you can press power (or wait) to boot anyhow. It would respond to me pressing power, but not go past that part. I was slightly concerned at this point, but lucky for me a long press of the power button and holding volume up - took me back to TWRP. So all was not lost.
I then decided to fully wipe everything again - following the previous steps I mentioned - and this time install the SR2-SuperSU-v2.79-SR2-20170103215521.zip from the thread "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)" By powerserge1 . This was installed immediately after the Rom zip. Then I wiped dalvik/cache and reboot. This time the phone did boot as described (AT&T logo and a few automatic reboots, before actually getting to the setup screen) - I was then on B180 with SuperSU installed. Unfortunately, wifi was not working!
So at that point I decided to flash the boot.img (inside the boot.zip) at the bottom of the first post on the thread "[Rom][11thMay]Ascend XT - Swift&Fast Slim B160/b170/b180 aio" By madvane20. I did this with my PC via Fastboot. At this point the Wi-Fi was fixed. Unfortunately while SuperSU was installed ( and I ended up updating it via Play Store) - Root was not working (tried root checker from the play store), and the SuperSU program was not actually functioning properly. But other than that the phone seemed fully functional, and up to date.
I should state now that I bought this phone just to use it as a cheap tablet (Wi-Fi only), I do not have AT&T Service - and did not try and unlock it. So I cannot speak to how it performs as an actual cellphone - Service quality, service features etc.
Of course, I felt a little uneasy about the phone working fine - but not correctly rooted. I don't really need root for my uses, but it's what got it actually booting in the first place, so I figure I may as well know it is working. So here's my last step...
I just simply reflashed the B180_Full_Update.zip in TWRP. Mounted everything, full wipe of everything and rebooted back to recovery - before flashing of course. I did not reflash SuperSU or mess around with the boot.img etc. Just a davlik/cache wipe before rebooting the system. This time the system booted fine (AT&T logo and a couple resets, like before) and wifi was working right off the bat. I was at B180 still (obviously), and no signs of root or SuperSU. This is fine by me.
SO after all of that, it seems I am on a stock (unrooted, all bloat) B180 version (from B130 or B140, no other versions in between). Updated fully via unlocked bootloader, and various software. I have not tried to root again, because I don't need it. I just do the basic debloating that android natively allows, disabling all the AT&T stuff and various built in apps I wont use.
Hopefully this will be some help to anyone following the same path that I have, or currently in any of the hangups I was in.
Also, for anyone trying to replace the Huawei Home Launcher with something like Nova Launcher (recommended) - be sure to go to Settings/apps/Huawei Home/Open by default then clear defaults. This will allow you to select a new default launcher.
Feel free to ask any questions, and I will help as best as I can!
Good outline! It's not all too hard to get going, most of the hassle is tweaking EMUI.
As far as your problem with supersu... Supersu, and magisk as well, work by patching the boot img - so when you flashed the default boot files, you uninstalled the part of supersu that does the work (though not the management utility that provides its interface). Also take care not to clear cache/dalvik immediately after installing magisk or supersu, as their installers often use it as a workaround to inject their system files. My advice: flas osm0sis's unSu script (forum/google search), reboot, reboot into twrp, reflash default boot img, clear cache/dalvik, flash supersu, and then reboot (can reboot back into twrp to wipe cache/dalvik again if you want, just verify supersu is working first).
Edit: use the most recent flashable version of supersu from its thread - installs aren't device-specific
Thanks for reading, and for the insightful reply - that does shed some light on things for sure.
I'm still not really interested in rooting the device, but if I decide that I need to - that should sort me out. I just have to make sure I reinstall SuperSU from TWRP, if I flash that stock (I'm guessing) boot image..
My main problem was that I wanted to get it the phone up to the latest software version, and I don't have an active AT&T SIM. Well, actually now that I think about it maybe I could have just used the gophone sim that was installed in the phone... hah! I am no stranger to flashing ROMS/Recoveries etc. so I didn't mind having to go manual to get the phone up to date. This phone is blessed in that you are able to unlock the bootloader - just sucks that I had to, just to get it on a later version of official software. I like keeping my devices stock, as much a possible - provided it meets my needs in that form. Obviously if It is what it takes to make a device usable, or bring it up from a software update abandoned state - I will use Custom ROMs, and ROOT features where needed. I try not to even waste my time with devices like that though, unless it is acquired for very cheap or free. There are just so many other choices out there, and the used market is very good to me.
I guess the thing that escaped me while doing research to start on this phone, was how best to get to the latest stock B180 software version - altering as little as possible to get there. The only direct solution that I found assumed (or required) that you were also rooted, and I didn't think about that in the right way. I just assumed that it wouldn't matter that I was not, and that a bigger problem might be that I was jumping a few software versions. I'll admit I kinda skimmed over that part that said "Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade." I just figured I didn't need root, so I didn't have to worry flashing Super SU. It makes sense now, due in no small part to your explanation!
I wonder if (starting at stock bootloader unlocked B140) I could have just flashed that B180 full update zip from TWRP, and then PC fastboot flashed that boot image - forgo flashing superSU in TWRP - and then be good to go (Wi-Fi Working as well)? Assuming I was not interested in being rooted of course. I'm guessing not, and I'm not sure why.
As a follow up... I started working on the other phone I bought - brand new, on B140 Software Version.
Unlocked bootloader > flashed TWRP > full wipe/format everything > flashed B180 zip > and fastboot flashed boot image - presto change-o! Stock B180 with wifi working fine (no root, as desired). Still have the unlocked bootloader message upon power on, but that's unavoidable. This is pretty much the most direct method for manually updating to the latest software version.
I also used DC-Unlocker Successfully on both phones for about $4 USD each.
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.
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
I think root is possible, but until now I have not been able to find out exactly whether the Fastboot is locked or not. it is my first OPPO and so I have no experience with OPPO. even if it's BBK. it's not an OP 8. We can only hope that someone might want to open it here. But from the root on youtube and other websites I would be careful. I also couldn't find any firmware for the flash via MSM tool or download tool ... so at the moment with an unbrick it is not possible to restore it.
__NBH__ said:
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
Click to expand...
Click to collapse
Factory reset should revert if the apps dont have revert option.
I'd like to see them show rooting an X2 Pro, rather than an A5s (CPH1909)
ordered one anyway... first phone without root in 11 years.. i hope i made the right decision.
It depends what you root for I guess. For me I currently root for adaway, viper, substratum themes and to change my font plus I recently run a module for various tweaks.
I used viper for my old wireless earbuds, I recently got new ones which sounds great without viper. Lots of apps now have a dark mode and I hear this phone has a beta mode that can turn other apps dark. Not changing font I can live with and the tweaks module is fun but not essential. Adaway I will miss. But for the first time in a while I'm not so fussed about root. I understand some people like it because you can flash ROMs when the device gets older. I survived for 18 months with a Samsung S8 plus without root so I know I can do it!
I need to decide whether to pre order the phone today or I miss out on the pre order bonus, I like it but don't think I can trade in my 7 pro, I love it a bit too much.
First and foremost adblock though you can do that without root. Second Sony Music magisk module for Android Auto. Third to debloat. 4th for some advanced Tasker tasks. I'm pretty sure I can get workarounds for most
Sage said:
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Click to expand...
Click to collapse
I don't see how this can be legit. The video shows a different device and also the rooting tool is for mediatek based devices. The Oppo find x2 pro is based on Qualcomm chipset.
Can anyone confirm if VMOS work this phone? It may be the only way to use root.
Never heard of vmos sounds interesting!
Yeah VMOS is like running VMware or Parellel on Mac. It's easier than rooting an actual android device, but it also gives more battery drain and less intuitive. I have it on my Mate 20 pro, does anyone know if it works on find x2 pro?
Videos been removed. I really wish this phone had working twrp and magisk it'd be literally the ideal phone
I'm just waiting for a oneplus phone with a periscope camera, that will be the one to get as it will be like this phone but with working root.
Yeah miss root. First phone in a decade I have bought without it. Though mostly I use it for adblock though private DNS works very well
Really missing root on this phone. I wish it were available considering the Snapdragon processor
EE
So far, i have been able to Enable USB Debugging and OEM Unlocking, this on the EE Network. Seems there is no TWRP Build Avail for the X2 Pro Yet. And i am unaware of any other way of Flashing the Magisk Zip Safely any other way.
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
bhomie28 said:
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
Click to expand...
Click to collapse
How did you manage to Patch the Boot IMG?
Thanks Man!
I download the OTA ozip file from oppo. Decrypted the ozip, extracted the boot image & patch it with magisk manager:laugh:
Easy going but how I can flash the file:crying: