Related
I have tried to install the 6.2.2 manually from the Amazon Website.
So i have downloadet the File and copy it to the Update Folder.
Now i have used the UPDATE Button. The Kindle makes a reload...and comes up again in the TWRP Menu.
So i make a reboot with the TWRP Menü, the same. Bootloop.
Is it not possiple to make a Update when TWRP is installed?
it is possible - but why do you want to do that ? - if the update from amazon installs then you loose fff,twrp and root
is'nt the nfx update that what you'r looking for ?
http://forum.xda-developers.com/showthread.php?t=1452082
if you'r then still in the twrp bootloop then issue:
adb shell
idme bootmode 4000
reboot
Yes you are right. I have done the Update from this post http://forum.xda-developers.com/show....php?t=1452082 a few days before and everything seems to be fine. But today, i will use Titanium Backup and it tells me. "You need to have SU installed..." etc.
So i make a reboot ---> TWRP is no more available.
Now i have rerooted with burito3.apk, but some Apps now closing with some error messages. So i thought i will make a recovery with TWRP to 6.2.1 and install the Update from Amazon.
And reroot with burito again.
Or i will istall the update from the link above, again.
Has someone the same issue with the Updatefiles from the Link. (It works a few days and then.....i´m back on the 6.2.2 without root and TWRP.
the thing with the nfx update files is a bit a mess - look through thread - i think someone reupped it
your link says page not found
fc's:
did you do clear dalvik/cache in twrp after installing the update as written in the op of nfx ?
if this don't help simply reinstalling the app should help
in trying to restore to stock with the original amazon rom some people messed up their shell and needed a factory cable - i would avoid to load the amazon rom
6.2.2 with CM7 ?
Hello, and thanks for all you do.
Is there an interest to update to 6.2.2 when you use CM7, waiting for CM9 ?
And please another question, How can I go to internet with CM7 in the normal format page, not the ones for mobile?
Thanks for your help
if you'r on cm7 then there's no interest - completely other rom
for your other question:
http://forum.xda-developers.com/showthread.php?t=1419751
thank you alot
I was trying to unlock my wifi tether by editing services.jar. I renamed both services.jar and services.odex by adding ".bak" I replaced services.jar with the recompiled one but didn't replace services.odex. now when my phone boots up I get "unfortunately verizon login has stopped" as well as a few others and I can't get in. What can I do to fix this? Its a verizon S5 with the march 31 kernel version.
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
fffft said:
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
Click to expand...
Click to collapse
I don't have a backup or custom recovery, I just used towelroot and thought it would be pretty safe to unlock the wifi tether. I think I forgot to turn on USB debuging so I think ADB is out of the question. Is there a way to "dirty flash" with Odin?
Edit: just did a reset with Odin, this fixed the problem. The phone was new so there wasn't much on it and I do keep my contacts and messages backed up so not much is lost except for the inconvenience of setting everything back up. I will definitely be more careful in the future.
Can anyone share it with me please? I see no one has uploaded it yet.
ahrion said:
I see no one has uploaded it yet.
Click to expand...
Click to collapse
Because the phone is not out yet! (In the west)
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
I'm no dev but I have to wonder, would the software have files written/coded in English inside of it. is it a convention ?
I would like to know if there is the possibility of installing the original firmware international version of axon7 Chinese model without root?
Unless the software checks at the start of the flashing process fail to match ROM with phone (so you don't try to flash a ROM for a different phone, which would brick it) it should work. As an aside, root/no root does not affect flashing, locked/unlocked boot-loader does but for ROMs signed by the manufacturer this isn't an issue either
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
abunhyan said:
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
Click to expand...
Click to collapse
expect ZTE releases the International firmware, then let's install on the Chinese model
I hope so......
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Schattenklinge said:
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Click to expand...
Click to collapse
It seems that a mismatch between the system and boot causes issues with WiFi.
thx i know, but with the 2 adb calls to modemst has not worked...
and i am not shure we i can flash the boot and the /system with the right img.
Below you will find my procedure to root the SM-G532F/G532G/SM-G532M Galaxy J2 GRAND PRIME PLUS/ Mediatek MT6737T.
This will root your device with SR3-SuperSU-v2.79-SR3-20170114223742
This procedure may work for previous and future firmware releases or it may not, however it is intended for the firmware versions as posted below. If you encounter issues simply flash the stock boot image included with the download.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
STATUS: Tested working
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the respective files below:
For SM-G532F based on AQD1 firmware- root_and_boot_sm-g532f
For SM-G532G based on AQC4 firmware - root_and_boot_sm-g532g
For SM-G532M based on AQD2 firmware - SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_31517
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to DOWNLOAD mode then connect your USB cable.
◘ 4. Run ODIN and place either SuperSU-v2.79-SR3_rooted_boot_sm-g532f_AQD1.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532g_AQC4.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_3151 as is in the AP slot. Don't change any options and hit START.
◘ 5. Wait for the device to flash and reboot.
◘ 6. Install the SuperSU apk from Play store and you should be rooted.
◘ 7. Have fun!
Credits: ME, @Chainfire and my tester @ShaDisNX255
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
ShaDisNX255 said:
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
Click to expand...
Click to collapse
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
ashyx said:
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
Click to expand...
Click to collapse
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
ShaDisNX255 said:
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
Click to expand...
Click to collapse
AQD2 is the latest.
Leave it with me.
ashyx said:
AQD2 is the latest.
Leave it with me.
Click to expand...
Click to collapse
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
ShaDisNX255 said:
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
Click to expand...
Click to collapse
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
ashyx said:
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
Click to expand...
Click to collapse
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
ShaDisNX255 said:
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
Click to expand...
Click to collapse
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
ashyx said:
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
Click to expand...
Click to collapse
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
Click to expand...
Click to collapse
Also, this seems to have broken my IMEI. I got IMEI unknown
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
Also, this seems to have broken my IMEI. I got IMEI unknown
Click to expand...
Click to collapse
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Not work for my phone
Everybody help me please
AlexEvans6 said:
Not work for my phone
Everybody help me please
Click to expand...
Click to collapse
What does that actually mean?
ashyx said:
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Click to expand...
Click to collapse
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
ShaDisNX255 said:
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
Click to expand...
Click to collapse
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
ashyx said:
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
Click to expand...
Click to collapse
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
ShaDisNX255 said:
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
Click to expand...
Click to collapse
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
ashyx said:
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
Click to expand...
Click to collapse
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
ShaDisNX255 said:
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
Click to expand...
Click to collapse
Data is the internal storage. It's separate from the system partition where the OS resides. Wiping data basically makes your device factory fresh as it wipes all user apps, settings and media.
In stock recovery it's labelled factory reset.
Every firmware has a recovery even the one you mentioned or your device just wouldn't boot.
If root apps are reporting not rooted then there is an issue somewhere. Quite likely it's encryption on the data partition that's causing the issue.
To remove encryption it is required to wipe data in recovery after flashing the boot image.
If it still doesn't work without encryption then I'm a little unsure of what the issue is as this procedure works just fine on Snapdragon and Exynos devices. It may be some kind of mediatek weirdness.
In any case I have an alternative method which should work, but involves an extra step.
At some point I will be looking at compiling twrp for this device, but I'd like to work out this root issue first.
For fast downloads go to updato.com
ashyx said:
What does that actually mean?
Click to expand...
Click to collapse
Idk help me please
Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.
Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.
Confirmed, it works on the cube (stark) as well...
That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.
Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.
2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.
How may I get the "su". It said, I don't have permision.
eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?
eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work
Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.
moving it to the right place.
anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?