Related
I noticed the audio level can sometimes be a little low, despite being at the same volume setting. Restarting the device seems to resolve the issue, though In looking for the audio settings it appears as though i don't have any audio options, i.e Histen sound and audio equalizer. These options were previously available under EMUI 5.1, but not on EMUI 8.
Any ideas?
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Paulo87 said:
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Click to expand...
Click to collapse
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
@mightyjcb :
What's your firmware version ?
C900B321 ?
mightyjcb said:
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
Click to expand...
Click to collapse
If your version is C432, i would suggest that you backup everything, plug it to your pc and restore your phone.
If you have a different version, it might be due to licensing. Best of luck :good:
oslo83 said:
@mightyjcb :
What's your firmware version ?
C900B321 ?
Click to expand...
Click to collapse
I'm using C432. Running b360a
mightyjcb said:
I'm using C432. Running b360a
Click to expand...
Click to collapse
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
oslo83 said:
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
Click to expand...
Click to collapse
I updated to Oreo B360 using the OldDroid method from what i think was the last update issued to Nougat OTA by Huawei/Honor.
I then installed LOS 15.1 and reverted back to EMUI 8 by flashing :
System (stock)
Recovery (stock)
KERNEL_B360a_TOUCH_FIX, then flashed the stock kernel over the touch fix image.
Mostly from your advice in thread https://forum.xda-developers.com/honor-9/help/oreo-nougat-recovery-stf-l09-t3760961)
No rebranding took place.
I have a sim card in the phone on the Giff Gaff network (Uses o2 infrastructure).
MCC: 234
MNC: 10
Cheers
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
oslo83 said:
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Click to expand...
Click to collapse
No viper4android has ever been installed. No bluetooth headset has ever been used with the device.
A full system wipe and stock recovery was necessary in order to go back to EMUI8 from LOS.
Paulo87 said:
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
Click to expand...
Click to collapse
I can try the restore using Hisuite on my PC later. In the meantime, using the 'Download latest full package' simply returns no update available. The same to pressing 'Check For Updates' on the System Updates page. Which i think is probably the correct behavior given that i am running the latest version available.
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
robenzo420 said:
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
Click to expand...
Click to collapse
I cant say for certain, but don't think i deleted that app.
Be interesting to know exactly how we both managed to do this to these devices. Sadly, i do not think there is the developer support available to answer it.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
robenzo420 said:
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
Click to expand...
Click to collapse
I believe you are correct. Rooting will mean that you are unable to update the device OTA. I am not so sure about OTA updates with the device unlocked.
robenzo420 said:
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
Click to expand...
Click to collapse
Then that is most likely the kernel image i referred to. It has a fix for buttons among other things. (If you want, you can flash the stock kernel image over the custom one you have now, and it will leave buttons active etc.)
As i say, this issue is now resolved.
YOU CAN FIND THE FULL G930AUCU8CSA3 FIRMWARE HERE:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
G930AUCU4CRE4 to G930AUCS4CRG5:
Download link: https://drive.google.com/file/d/1MoJ0be2exLMoji2ZURR6tbEiHCqWSszG/view
G930AUCS4CRG5 to G930AUCU4CRI2:
Download link: https://drive.google.com/file/d/1Fdrcy4m49Qtl-__dUE0Etuqmyn8UhYbe/view
G930AUCU4CRI2 to G930AUCS8CRJ2
Download link: https://drive.google.com/file/d/1bhVx5Rt_CTXmG5YQrY5azS10RO3lWj1r/view
G930AUCS8CRJ2 to G930AUCS8CRK1
Download link: https://drive.google.com/file/d/1lepPXVZIiZM4i_VMOUOvDvVHvGY4ifwv/view
G930AUCS8CRK1 to G930AUCS8CRL1
Download link: https://drive.google.com/file/d/1CUJOVWnDsk3LL378vxLO0vp8y3AdQjmr/view
If i helped you don't forget to hit thanks button
G930aucu4cri2
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Juliowwwe said:
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Click to expand...
Click to collapse
Link is UP
thank you very much
thank you very much
New October update is UP
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
lahlah said:
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
Click to expand...
Click to collapse
1.) Turn off the phone. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
2.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
3.) Make sure you have ADB and the proper drivers installed on your PC:
http://dl.adbdriver.com/upload/adbdriver.zip
4.)Put the firmware in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
5.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file).
6.) Wait patiently.
7.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
samhnky said:
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
Click to expand...
Click to collapse
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
stek-kravari said:
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
Click to expand...
Click to collapse
Awesome! Thank you, thank you!
I actually really like Oreo, just trying to get Oreo and WiFi calling working on my phone (My Office at work fights all day for 1 bar of cell signal), I had hoped that WiFi calling worked in the SM-G930U variant since everyone talked about it running so much better, but alas, it still doesn't support WiFi Calling (Stupid me for thinking it might have had support added recently).
Thank you again
(My Wife is sure to get upset with me once again working on my phone again today... whoops)
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
bnn0 said:
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
Click to expand...
Click to collapse
You mean about G930AUCS8CRJ2 sideload with adb? Im just pulling the update from AT&T servers and uploading it here. I don't know how to make sideload zip. And for the rooting part I don't know if its possible now because the bootloader binary was updated to 8, try to search here on xda and see if you can find root methods for this firmware
new update, check first post
----
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Maury Yarik said:
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Click to expand...
Click to collapse
First you need to install this:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871 (G930AUCS8CRJ2)
Then you need to go from G930AUCS8CRJ2 to G930AUCS8CRK1, G930AUCS8CRK1 to G930AUCS8CRL1 and you will have the latest update.
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Josh13400 said:
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Click to expand...
Click to collapse
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
stek-kravari said:
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
Click to expand...
Click to collapse
I was thinking something like that was possible. I have baseband version G930AUCU4CRB5 Android 8.0.0 on the AT&T Gal S7 as mentioned, I never saw any updates from this version to go up to a newer version or get into regular updates from OTA. 2 issues I would like to also fixed, that came with the manual update to 8.0 oreo on my phone was the HR heart rate sensor on the back by your flash(red LED) always goes off.. And have tried to go to Samsung health and do some settings to turn it off, but seems to show back up eventually. Also, the issue of not having a working LED indicator, works fine when the phone is POWERED off. and charges. But in OS, it won't work, screen off or on bc of the update. If anyone knows how those issues could be fixed and if there is a possible newer update from my baseband mentioned below. And thanks for the response.
HI, Help needed
Hi,
I wanted to check if it is possible to flash the latest Oreo firmware you have here for downloading dirrectly to my samsung s7 that is currently running on 7.0? Current BaseBand is G930AUCU4BQK2
Basically what happened was that i lost all my contacts on my phone, I ended up download Dr.Phone to my laptop, which i used to try and recover my numbers. What i didnt know was that dr.phone rooted my device which has caused me nothing but headaches.
I now want to flash my phone and get updated to oreo and have my phone working normally again. Since dr.phone did whatever it did to my phone I lost use of my finger print scanner, had to disable samsung health as it kept trying to open on its own, my phone is lagging and freezing constantly..
I just want my phone to be normal again and unrooted and updated.
Lastly my phone is an AT&T device, that i bought second hand in Dubai, if i flash stock firmware is it going to carrier lock my device to AT&T again?
Any advice and help with this matter would be greatly appreciated.
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.
Hey guys.
Has anyone managed to root the new Nvidia Shield TV (2017) 8.0 pie update with Magisk?
I tried it in fastboot mode with an magisk patched boot image, (extracted from full upgrade zip) but that causes a bootloop.
I also rooted my shield with Oreo the same way.
You have to wait for the developer image which isn't out as of right now.
AngryManMLS said:
You have to wait for the developer image which isn't out as of right now.
Click to expand...
Click to collapse
Ok thanks. I have it done like this with 7.2.3 update. Extracted boot.img from full official update zip (not dev image). But I will wait for dev image.
I actually just downgrade to 7.2.3 and root the device again best option for me to go back im gone wait until thay fix the root with the new update
rorm2010 said:
I actually just downgrade to 7.2.3 and root the device again best option for me to go back im gone wait until thay fix the root with the new update
Click to expand...
Click to collapse
Did you have any problems downgrading?
No just flash the 7.2.3 and after that go to bootloader and just do the factory reset and reset your device and every thing should be ok and you know how you do the root and the other things
rorm2010 said:
No just flash the 7.2.3 and after that go to bootloader and just do the factory reset and reset your device and every thing should be ok and you know how you do the root and the other things
Click to expand...
Click to collapse
Hi everyone, i accidentally upgraded by mistakingly pressing a button and even though i unplugged the shield it was too late. I was fully rooted, and on android 8.0 while i have lost root my bootloader is unlocked. For all those that have downgraded, did you flash the 7.2.3 dev image from the nvidia site? In otherwords did you just re-follow the rooting steps? And since my bootloader is unlocked, i just go ahead and reflash using ADB correct?
Not the dev one it is the normal one and the root it is same root on the 7.2.3 magisk
After you flash back the rom dont lock the bootloader just do the factory reset and reboot your device and start with root tutorial
this isn't a post for developer section... just an fyi... to top it off your title is misleading as it almost looks like you are going to tell people how to root but you are simply asking others if they have done it lol questions/guides etc. etc. should go in Q&A or General sections..
About Magisk:
Magisk not work on Shield Android TV PIE because in PIE you don't have ramdisk inside boot image. PIE have system_as_root partition layout. The developer of Magisk, for Android devices that born with Android version < pie, like the Shield TV, install the magisk in the recovery and if you need root, you must start the phone / device from recovery with power and volume buttons. Have Magisk in recovery, clearly is not a good solution for shield tv because enter in recovery on a box is not so easy like on a phone. The solutions can be, or made a pre-rooted firmware, or create a firmware that restore the previous partition layout.
Full Android PIE is already in preparation.
UPDATE 07 august 2019
Full Android PIE is out
elliwigy said:
this isn't a post for developer section... just an fyi... to top it off your title is misleading as it almost looks like you are going to tell people how to root but you are simply asking others if they have done it lol questions/guides etc. etc. should go in Q&A or General sections..
Click to expand...
Click to collapse
Yes sorry. I will change it. Can I move it myself or just you?
zulu99 said:
About Magisk:
Magisk not work on Shield Android TV PIE because in PIE you don't have ramdisk inside boot image. PIE have system_as_root partition layout. The developer of Magisk, for Android devices that born with Android version < pie, like the Shield TV, install the magisk in the recovery and if you need root, you must start the phone / device from recovery with power and volume buttons. Have Magisk in recovery, clearly is not a good solution for shield tv because enter in recovery on a box is not so easy like on a phone. The solutions can be, or made a pre-rooted firmware, or create a firmware that restore the previous partition layout.
Full Android PIE is already in preparation.
Click to expand...
Click to collapse
So it's like new Samsung s10 devices now? This is weird because with my OnePlus and pie it works.
But thanks for the info
Is Magisk fixed yet for this? I tried loading Magisk 20 but ran into a boot loop.
you shouldve posted this in q&a...
Shield Tv 2017 with Developer image 8.2.2 + Kernel Performance PIE by @rootfan,works just fine....Thanks to all involved,especially @rootfan for great kernel.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Starting with 6.2.6.6, Magisk is always installed.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
Thanks to @k4y0z and @xyz` for the unlock.
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Changelog and Downloads:
October 24, 2021 - 6.2.8.1_r3 (md5sum: 3795edc2d640932a88da39da8a0811c5)
July 17, 2021 - 6.2.8.1_r2 (md5sum: e9e37a2d485a3397df041938818421e9)
This includes updated tz firmware to fix the device locking up when trying to play video.
April 3, 2021 - 6.2.8.0_r1 (md5sum: 2efdfc5728caba2953a351a082023a59)
December 26, 2020 - 6.2.7.7_r1 (md5sum: b835e29bb29458004063121a422c1bf7)
May 3, 2020 - 6.2.7.1_r1 (md5sum: 56ec885e5bd258682c90e8f08371301d)
November 10, 2019 - 6.2.6.8_r1 (md5sum: 8cdc16239df36c8640004232918c5477)
October 19, 2019 - 6.2.6.6_r1 (md5sum: df8f3d033fddf66a1b4aa3a6b228196b)
Starting with this version, Magisk will always be installed.
This includes updated tz firmware to fix LICENSE_ERROR with Prime video.
October 13, 2019 - 6.2.6.5_r1 (md5sum: bdde0303d8db5495ac6dc2aaf476d2f4)
Awesome!! Thanks!!
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
vasir13 said:
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
Click to expand...
Click to collapse
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
rbox said:
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
Click to expand...
Click to collapse
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again
Thank you, I feel safer already.
Any idea what version of gapps would work on this? Also, any idea if installing nanodroid, patched playstore & patching the ROM for signature spoofing be dangerous (as in bugger up the BL/TWRP)?
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Hi,
I successfully installed the hacked bootloader and TWRP a few days ago, but I did not do anything else. I was still on the original 6.2.5.8 version.
Today I wanted to flash the prerooted 6.2.6.5 and I can't manage to boot it (and since I did not expect problems, I did not make a backup of the old system). I cannot go past the "firetv" boot logo and in this stage "adb logcat" is not yet working, so I don't see any logs.
First boot was just installing the ROM. Second boot with previously wiping Cache / Dalvik. Finally I wiped also data (and Cache/Dalvik again). I cannot get past the boot logo.
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Thanks Tim
tehlers said:
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Click to expand...
Click to collapse
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Sus_i said:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Click to expand...
Click to collapse
Yes, I have checked MD5 on my notebook after download, but not after pushing the file to the stick. I will do that now and post it here (with edit). But I doubt this being the issue.
EDIT: MD5 of the zip in the stick is also ok.
tehlers said:
EDIT: MD5 of the zip in the stick is also ok.
Click to expand...
Click to collapse
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Edit: Have you flashed the magisk.zip behind the ROM?
Sus_i said:
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Click to expand...
Click to collapse
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
EDIT: As I said in the first post, I did not do anything with the original ROM, except flashing the hacked BL and TWRP, no Magisk or whatever.
Best
Tim
tehlers said:
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
Best
Tim
Click to expand...
Click to collapse
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Sus_i said:
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
Click to expand...
Click to collapse
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
T1inkering said:
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Click to expand...
Click to collapse
for example with ADB / TWRP Commands, something like that...
Code:
adb push ~/Desktop/mantis-6.2.6.5-rooted_r1.zip /sdcard/
adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.5-rooted_r1.zip
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
tehlers said:
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
Click to expand...
Click to collapse
It is mentioned.. but not thats an issue without flashing magisk
Sus_i said:
It is mentioned.. but not thats an issue without flashing magisk
Click to expand...
Click to collapse
That's what I mean. It's not mentioned that you need Magisk in any case (to boot the image as such *and* probably also to get root [which is not prerooted then?]).
Thanks again!
puppinoo said:
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Click to expand...
Click to collapse
I reply to myself and happy to confirm I installed this "generic" image to my US Stick 4K and after I accept terms of use *Italian* Alexa and Prime video seem to wotk fine.
If I remember well my previous image was the 6.2.5.8 (basically the one I installed when the exploit for Fire TV Stick 2 (Tank) was released but can't be 100% sure.
Now I have to try it on my *Italian* Stick 4k (bought on amazon.it).
Amazing and thanks a lot again.
Puppinoo.
So great to see @rbox 'es prerooted roms for the Fire TV Stick 4k
There are some things that I am not familiar with:
1. What is magisk for and what if I don't install it?
2. Does root not work without magisk?
On the older Fire TV Devices we did never have to install magisk or so and it was prerooted with rboxes roms and root was working. Why is everybody talking about magisk? Can magisk break anything or be critical like xposed was on the Fire TV 2 box? I remember that xposed framework was a pretty messy issue for recent Fire TV 2 (Sloane) pre-rooted roms. Magisk seems to go deeply into the system, similar to xposed framework, isn't it?