I have the variant of this phone by boost Mobile. There is so far as I can tell no way to do a normal bootloader unlock procedure on this device. So I have been trying to experiment trying to break or disable verity. Before I get any more excited, let me make sure I understand correctly. None of the partitions for example system, or boot or recovery cannot be flashed while verity is enabled, most certainly if you don't have root access on the device.
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9). So I guess my question is, if I am able to repeat this process then how good is it that I am able to flash a system image and How likely would I be able to continue flashing the other partitions? Before I get into detail on how I managed or how I think I managed to do this I want to make sure that this can actually go anywhere before I waste my time.
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
i rooted it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
What files did you flash through odin?
sikkinixx said:
What files did you flash through odin?
Click to expand...
Click to collapse
only the ones I am able. Still haven't figured out how i downgraded from 10 to 9. I flashed the stock firmware (AIO firmware. apparently all carrier stock firmware can be flashed, regardless if its Boost Mobile [BST]). I however did flash the modem (CP) with modem.bin and modem_debug.bin from a combination firmware that's supposed to be factory binaries (which I can't flash any others from that combination because it tells me to get permission to flash them lol).
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
majored said:
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
Click to expand...
Click to collapse
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
DragonFire1024 said:
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
Click to expand...
Click to collapse
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
majored said:
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
Click to expand...
Click to collapse
It depends. So far I have only been able to use a different modem image and nothing else. Even if I flash the images that do match the flashed files that fail checksum, it still fails secure check. What i am confused about is how I am able to flash anything and even get a check sum failure. I was under the impression that images that fail anything, check sum or secure check, won't flash. So my question is how is it I am able to do so? If something is flashing there has to be a way to flash the files it needs.
So I have successfully made kingroot device owner. Not that it does any good because it doesn't seem to give me root. But using one of my favorite apps to seek the activity
Code:
com.kingroot.kinguser/.receiver.DeviceOwnerReceiver
I used dpm to set-device-owner. I did this from the most recent available firmware for this device on a fresh factory reset with no accounts attached.
Before that I also was able to make icebox apps freezer device owner and disable knox apps.
If anybody knows any other tricks I can use for device owner or something that can escalate privileges from here...
I love icebox apps freezer. You can set it as device owner and have the ability to freeze all applications Including system apps. I have been doing so one by one and as I do, some of Samsung's UI disappears and stock Android fills in. This is probably as close to root as I'll get for a while.
DragonFire, which files did you change in order to obtain root? I want to try this out for myself. Please respond
Nothing in the thread mentioning what files he flashed?
for anyone who needs to test code on this type device i have a sm-a102u1 unlocked running android 9 i wont send it off but i will test anybodys wierd root code maybe this exploit could work https://github.com/grant-h/qu1ckr00t let's make history guys i will be the dude who doesn't know what hes doing somebody compile this and tinker with it all you want and send it off to me to test i think CVE-2019-2215 will be our best bet of pwning this sucker i got a laptop running windows 10 for all your needs so if you like just wanna help but dont have the device or dont wanna brick yours be my guest
and even if you have almost 0 coding knowlage feel free to send your abomnation of a rooting software to just get it tested no matter how bad it is
even if you don't have the device
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
Sounds like debugging level needs set to Mid or High from the stock setting of low. This can be done and allow the root to stick until a user reboot.
Applying that whole method After, setting debug level, might actually work. It did for the Note5.
At that point, once root is achieved, it really comes down to making sure all partitions are mounted with the same options.
You can't just remount system as read/write only, if that partition normally has "noatime, etc" mounting options. That automatically triggers a verity panic reboot
You got to do the profit work, as well as, get every letter down to the T as far as copying stock fw. File names in Odin, CB, QL, Date fingerprints, file size to the byte (almost).
It's possible to spoof ALL Day, but most don't think (aka Over Think) all the possible checks and balances that would deviate from a standard stock download/flash.
DragonFire1024 said:
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9).
Click to expand...
Click to collapse
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Delgoth said:
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Click to expand...
Click to collapse
strange how he didnt post anything on how he did it
timba123 said:
If we pay $50 to $75 for a flash token, maybe factory combo could be flashed then root figured out from there but its not worth it to me to spend that for this pos. So stuck with adb debloat I guess. Oh well
Click to expand...
Click to collapse
I mean, after upgrading, yeah the A10e is a bit dated. BUT WAIT...
The A10e is still a device using an Exynos octa-core SoC. Not a snapdragon or mtk chipset. With full command line access and root privileges the hardware itself is actually still quite capable with its 2gb of RAM.
Related
I've compiled the stock firmware for the Developer edition of the Galaxy S4. Specifically the 1545OYUAMDK variant that shares similarities to our beloved MDK. I got the partitions from users who had made backups prior to gaining root and/or other means to have the least modified version of the stock firmware. As far as the bootloader goes, I have the entire firmware and I edited the partitions to account for the padded zeroes and offsets. Below is a table of partitions, the green are those that I or dev edition owners were able to successfully flash with Heimdall/Odin and are signed, the red are ones that I am unable to flash probably because I incorrectly edited them to be consistent with the sha1 checksums of partitions verifying it immediately before or after or haven’t been tested by someone with a dev device.
I should note that I only tested this on a stock root ME7 build, therefore some partitions that I couldn't flash, the Dev edition of the Gs4 might be able to. I did confirm that users on OYUAMDK were able to flash certain parts of the firmware but no one has tried to completely go back to stock. As expected, I could flash all but recovery, boot, and aboot, djrbliss mentions that the difference between consumer and dev builds comes down to how aboot checks boot and recovery in his blog...so my findings are consistent with his research. I confirmed that the partitions that I did flash were actually flashed because I compared the hexdump of the files before and after (since the file sizes are mostly the same after cutting out the padded zeroes and other indicators). If you have a developer device and you absolutely need to flash stock firmware, this is probably as close as you will get, but more work needs to be done to refine this. Note, take precautionary measures and especially be careful when flashing aboot. Feel free to criticize these, and let me know if any changes need to be made. Use at your own risk and remember this is somewhat a work in progress.
Edit: One user on a dev build brick claims to have flashed aboot.mbn successfully. Status changed to yellow! (Need one more confirmation before I feel confident to give it the green light, pun intended)
Instructions:
Note that this is more meant for a emergency rather than convenience, also the purpose of this post was both to help the owners of development edition gs4 and to make the process better in the future, this can brick your device
If you do decide to dance with the devil, post your findings. The file is in tar.md5.gz format so odin will extract it to a tar.md5 for you or you can just flash it in heimdall. I have left the firmware.xml and pit file in the tar, you can remove them and edit them as needed.
Using Odin: Odin doesn’t play well with this. I’ve had varied results. Use Heimdall. But if you insist..have the latest Samsung drivers, try Odin versions 3.07+, make sure to run as administrator and select/click PDA then select the tar.md5.gz file. Also make sure that only "Auto Reboot" and "F. Reset Time" are checked before finally clicking start.
Using Heimdall: Load the package using frontend running as root. If you use Heimdall in the command line, then you probably already know what you're doing.
RECOMBINATION_I545OYUAMDK_562219_STOCK_RESTORE.tar.md5
MD5:b238ac352255f3b26593dffa6d7aa72f
Download
Download Mirror
Size: File/Partition:
2597816 RECOMBINATION_I545OYUAMDK_562219_STOCK_RESTORE.tar.md5
8 SGR.pit
2518320 system.img.ext4
9000 NON-HLOS.bin
9488 recovery.img
208 tz.mbn
1200 aboot.mbn
50856 modem.bin
268 sbl3.mbn
152 rpm.mbn
96 sbl1.mbn
4 firmware.xml
8072 boot.img
152 sbl2.mbn
Before I get asked "What happens when people on MDK or ME7 try to flash this"?
I'll tell you my results, from numerous flashes in odin/heimdall. My baseband and build type are both now OYUAMDK as shown below and my phone doesn't show a custom screen nor does my phone think its modified. However this doesn't change the fact that we cannot downgrade to a older kernel. This will not unlock your device if you're on MDK or ME7 and flashing this carries a high risk of bricking your device. When flashing the stock MDK restore, ME7 users usually get a "SW REV. CHECK FAIL: FUSED: 3, Binary: 1" message, however with flashing this on ME7 users will receive a "SECURE CHECK FAIL: aboot" message instead either way its a fail.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
**
Changelog
10/14/2013 - Initial release
10/19/2013 - Confirmed boot.img and recovery.img flash succesfully - status changed to green
11/09/2013 - User claims to have flashed aboot.mbn succesfully on dev build - status changed to yellow!
Awesome Surge! Now somebody with a Dev ed device on me7 like sound-mind should try it and see if they could restore their device to developer...
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
I am new to Heimdall. I am running it on a Windows 8 64 bit machine. Heimdall does not see the tar.md5.gz file....it seems to be looking for a tar.gz file. What am I doing wrong or what do I need to do. Thanks. This is a great resource to have,
Skeetch79 said:
I am new to Heimdall. I am running it on a Windows 8 64 bit machine. Heimdall does not see the tar.md5.gz file....it seems to be looking for a tar.gz file. What am I doing wrong or what do I need to do. Thanks. This is a great resource to have,
Click to expand...
Click to collapse
Download 7-zip or winrar. Then extract the tar.md5.gz so it leave you with just a tar.md5. Then either:
1. Rename it to a tar, extract the files, and customize the package you want to flash using heimdall then heimdall will make a tar.gz for you
or
2. Rename the tar.md5 to tar, then using 7-zip in the right click menu or from the 7zip file manager menu select "add to archive" and under archive format select gzip.
Alternatively you can use the tar.md5 with odin, but I highly suggest using heimdall instead. I've had odin flash the file for me, but more often then not it fails for this particular odin tar.
Great! Thanks!
Sent from my SCH-I545 using Tapatalk
Extraordinary progress and dedication and effort. Thank you so much!
So the file includes everything a stock Dev ed official Odin image would right? The red partitions are there even though you could not manage to flash them..
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
Roland_D said:
So the file includes everything a stock Dev ed official Odin image would right? The red partitions are there even though you could not manage to flash them..
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the red partitions are still there. But as to whether it includes everything? Technically no, the cache.img.ext4, persdata.img.ext4, and hidden.img.ext4 arent there yet. Im going to have to look more into hidden.img.ext4 because Id include it but. As far as cache.img.ext4 and persdata.img.ext4 I haven't come across a clean copy of either yet. I thought about just usings MDK's but ill look into it more before I include any more partitions.
Upon opening Heimdall I notice that I have the options to Load Package, Flash and Utilities but "Create Package" is greyed out. How does that become enabled?
Skeetch79 said:
Upon opening Heimdall I notice that I have the options to Load Package, Flash and Utilities but "Create Package" is greyed out. How does that become enabled?
Click to expand...
Click to collapse
I haven't used Heimdall in Windows but in linux you have to go to utilities, click detect device, then select save as and save the .pit file. Im not sure if the Windows version of Heimdall has a command line either but if it does you could also type the equivalent of this:
sudo heimdall download-pit --output dev-SCH1545.pit
Click to expand...
Click to collapse
Then go to the Flash tab and under pit click browse and open the pit file you just downloaded. Then click add-->select a partition name-->click browse and navigate the the selected partition file-->Then click add. Now you should be able to use the Create Package option.
Surge1223 said:
Yes the red partitions are still there. But as to whether it includes everything? Technically no, the cache.img.ext4, persdata.img.ext4, and hidden.img.ext4 arent there yet. Im going to have to look more into hidden.img.ext4 because Id include it but. As far as cache.img.ext4 and persdata.img.ext4 I haven't come across a clean copy of either yet. I thought about just usings MDK's but ill look into it more before I include any more partitions.
Click to expand...
Click to collapse
My Dev edition has no modifications, not sure if that helps or not. I'm willing to post what you need as long as it doesn't contain any personal info.
I'm unable to download due to dropbox temp disabled
equake said:
I'm unable to download due to dropbox temp disabled
Click to expand...
Click to collapse
Yeah im in the process of changing file hosts, ill put up a temp mirrror though
Sent from my SCH-I545 using xda app-developers app
This is a great resource and compilation for Dev S4 owners. Have you made anymore progress with this or found anything more? Thanks again for all your hard work and dedication
Well I haven't heard from anyone regarding where heimdall is failing. I also haven't confirmed if people on Dev s4s that took the ME7 update were able to downgrade back to OYUAMDK or not. So far the radio and kernel along with sbl1-3, rpm and tz have been proven to work. I know recovery should work, as I'm able to take it apart successfully, and the build.prop says OYUAMDK. I'm hoping aboot works, aboot is the partition I'm waiting for results on.
Sent from my TouchPad using xda app-developers app
I thought
I was pretty much stock with root (stock recovery and boot images from Bait-Fish and yourself in the other thread) but I constantly had the custom and open lock icon screen when booting the phone. I was reluctant to load ROMS at this point without any sort of safety net (I did make a nandroid early on in case) - even though it is a developer phone and that is what you are supposed to do
I wanted to try the package you put together so I played it safe and just created a Heimdall package to flash the Boot and Recovery only. Flashing went great and now when I boot the phone I get the Samsung S4 boot screen along with the word "official" under about phone->status in the system settings. (if flashing boot and recovery did not work then i would have went as far as flashing the system.img.ext4 - so now I don't have to)
As I said, I flashed both the boot and recovery images posted by Bait-Fish and yourself in the other thread and stayed on a custom status but somehow these boot and recovery images did the trick.
Thanks again.
If you need me to test anything out please let me know.
It would be nice though if the S4 Developer Phone could received OTA's and/or have KIES recognize the phone. Being on MDK we are two builds behind the consumer version with no official way to upgrade and catch up. could I flash the consumer ME7 or MI1 build without worrying about locking the bootloader and my dev phone? If so, then could I always ODIN or Heimdall back down to MDK if I wanted to?
Edit: the recovery and boot images I downloaded from bait-fish were identical in size... does that make sense or should they be different?
Skeetch79 said:
I thought
I was pretty much stock with root (stock recovery and boot images from Bait-Fish and yourself in the other thread) but I constantly had the custom and open lock icon screen when booting the phone. I was reluctant to load ROMS at this point without any sort of safety net (I did make a nandroid early on in case) - even though it is a developer phone and that is what you are supposed to do
I wanted to try the package you put together so I played it safe and just created a Heimdall package to flash the Boot and Recovery only. Flashing went great and now when I boot the phone I get the Samsung S4 boot screen along with the word "official" under about phone->status in the system settings. (if flashing boot and recovery did not work then i would have went as far as flashing the system.img.ext4 - so now I don't have to)
As I said, I flashed both the boot and recovery images posted by Bait-Fish and yourself in the other thread and stayed on a custom status but somehow these boot and recovery images did the trick.
Thanks again.
If you need me to test anything out please let me know.
It would be nice though if the S4 Developer Phone could received OTA's and/or have KIES recognize the phone. Being on MDK we are two builds behind the consumer version with no official way to upgrade and catch up. could I flash the consumer ME7 or MI1 build without worrying about locking the bootloader and my dev phone? If so, then could I always ODIN or Heimdall back down to MDK if I wanted to?
Edit: the recovery and boot images I downloaded from bait-fish were identical in size... does that make sense or should they be different?
Click to expand...
Click to collapse
I can think of no circumstances where I would want my Dev Edition S4 to receive OTA Downloads. I want to avoid those. That is why I bought a developer device to start with. When the Devs have had a chance to see the updates features and incorporate them into new ROM releases that is soon enough for me. If indeed the OTA could be had without locking down the bootloader, I still would not want to accept it. So much goodness in custom roms. I don't consider myself behind at all if I wait for the latest updates to be incorporated into the Roms.
But TEHO, I guess.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
I can think of no circumstances where I would want my Dev Edition S4 to receive OTA Downloads. I want to avoid those. That is why I bought a developer device to start with. When the Devs have had a chance to see the updates features and incorporate them into new ROM releases that is soon enough for me. If indeed the OTA could be had without locking down the bootloader, I still would not want to accept it. So much goodness in custom roms. I don't consider myself behind at all if I wait for the latest updates to be incorporated into the Roms.
But TEHO, I guess.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
I hear you! What ROMS are you running and usually how do you go about installing them? (i.e. install custom recovery then flash the ROM as a zip?) I am pretty new to having a developer device and navigating around it. Does Hashcode's SafeStrap work for our dev device? if so, which version? Sorry I am asking so many questions, I am still a n00b, still green, getting my feet wet, I want to make the right decisions and do the right things without royally screwing anything up.
Skeetch79 said:
I hear you! What ROMS are you running and usually how do you go about installing them? (i.e. install custom recovery then flash the ROM as a zip?) I am pretty new to having a developer device and navigating around it. Does Hashcode's SafeStrap work for our dev device? if so, which version? Sorry I am asking so many questions, I am still a n00b, still green, getting my feet wet, I want to make the right decisions and do the right things without royally screwing anything up.
Click to expand...
Click to collapse
In regards to your question about installing ME7 or MI1 I would highly advise against it. We're currently trying to see if someone who already took the ME7 update on their dev phone is willing to test and see if this package will take them back to OYUAMDK, specifically if it will allow them to flash an older aboot. It does not work on consumer ME7 devices, but until we have confirmation from someone who is already on an ME7 build on their dev device, id hold off. As far as custom recovery...I believe you guys have the ability of using loki and/or just regular non loki'd twrp and cwm right? Id use those before I would use Safestrap at this point; more compatibility. Also if you wanted to be on the latest build why not install a ME7 rom? VRUAME7 stock root deodex is already up. I was working on the MI1 stock root deodex rom, but got side tracked lol. Its pretty much done, just cant get wifi to work all time yet. Oh and about the recovery and boot imgs and different sizes, they should be identical the only difference is I trimmed the padded areas, basically the same as you would get from an official Odin image.
**WARNING** I TAKE NO RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOU, YOUR MOM, YOUR DEVICE, OR ANYTHING ELSE THAT HAPPENS IN YOUR LIFE AS A RESULT OF FOLLOWING ANY INFORMATION/INSTRUCTIONS I OR ANYONE ELSE POSTS IN THIS THREAD. EVERYTHING YOU DO IN YOUR LIFE IS AT YOUR OWN RISK AND THIS IS NO DIFFERENT. DO NOT CONTINUE IF YOU'RE GOING TO BLAME ME FOR ANYTHING AT ALL.
This is mostly going to pertain to the oem.prop file located in /oem on your device because that's where my work ended up taking me.
So in my research and impatience I've discovered a few things about the Amazon variant of the Moto G4:
The 32GB model of the Amazon variant *can* be bootloader unlocked, just follow the normal instructions.
The athene_amz descriptor in ro.product.name in oem.prop prevents Amazon variant users from installing stock ROMs not specifically meant for the Amazon variant.
ro.product.name in oem.prop can be modified.
Some things I'm working on:
Trying to find a copy of the non-Amazon oem.prop.
Seeing if there's anything else that needs to be done to the Amazon version to show completely as the default USA model.
Some questions:
Is anyone willing to send me a copy of their oem.prop from their standard Moto G4 USA/NA oem.prop?
I'm having some radio/SIM issues with AOSP/Lineage-based Nougat ROMs, I'm on a Sprint-based MVNO. Is anyone else having these issues?
After modifying oem.prop which stock ROMs work with the Amazon variant?
Does anyone have a more efficient way of mounting /oem? My method will be described below.
That's it for the lists, I just thought since some of this stuff was new or not well organized that I'd make it easy to understand my key points.
The reason you would want to modify oem.prop, which contains the basic information about your device no matter what ROM you have installed, is because when you try to install stock ROMs they check for at least these 2 things: They check your phone's model and your currently installed firmware. I believe the soak test release looks for the latest available version of Marshmallow (64/65), which should be the same as the Amazon variant... but even with an unlocked bootloader it will still refuse to install because instead of showing up as just "athene" in oem.prop it shows up as "athene_amz" and refuses to install. For the Indian release it looks for an *older* revision of Marshmallow (63/64) and refuses to install for that reason and because of the ro.product.name descriptor in oem.prop. If you're looking to install a stock ROM besides the Amazon versions it's imperative to make these changes. There are a few other reasons as well. I've seen people talk about successfully relocking their devices, I haven't done any research on this but if you're looking to sell or gift your device you may possibly be able to fully convert it to a standard Moto G4 using the non-Amazon ROMs and update line through these means.
So here's what I did to modify my oem.prop:
Find and download a stock ROM for a Moto G4/Plus variant you know to be incompatible with your device (I used the soak test).
Plug phone into computer via USB.
Push the zip file to your phone/SD card.
Reboot to custom recovery (I'm using the latest TWRP).
Attempt to flash ROM.
Go to your PC and open up ADB shell.
Enter the command
Code:
mount -o rw,remount,rw /oem
Via ADB shell navigate to /oem and pull oem.prop
Create a back up of oem.prop on your PC for posterity. I highly recommend that you do not skip this step.
Open oem.prop on your PC and change all instances of "athene_amz" to "athene" (without any quotes).
Rename the oem.prop on your device to oem.prop2.
Push your modified oem.prop to /oem
Enter the command
Code:
mount -o ro,remount,ro /oem
Enjoy your new ability to flash non-Amazon stock ROMs!
A few notes:
The reason I had to make an invalid flash attempt is because I couldn't figure out how to get /oem to mount otherwise. Normally the folder appears completely empty and I don't know where the files are nested in the filesystem. Even using the mount command I was unable to do so.
I have yet to install a stock ROM on my device because after unlocking my bootloader I immediately flashed Lineage thinking I'd have no issues with it. I did have issues and I had read something that lead me to the impression that I had to flash a modem file to my phone to get it to work properly. After being unable find it I went in search of a stock Nougat ROM thinking the update from that might flash the necessary firmware. The error from that attempt is what lead me to figuring what I've posted about oem.prop... but sadly in order to install ANY stock ROM I'll need to go through the lengthy downgrade process... which I will as I experiment but since this G4 is my primary device it'll be some time before I get too deep into it. Lineage works fine enough for now. Hopefully there's a fix soon. But it's worth stating that the reason I was refused the stock ROMs is because of the installed ROM version rather than the variant as it was before.
Whoa, thanks for this information!
But can we change it in the rom we want to install?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lerg96 said:
But can we change it in the rom we want to install?
Click to expand...
Click to collapse
I'm wondering if changing that file will allow us to get on the correct upgrade path
---------- Post added at 02:31 PM ---------- Previous post was at 02:23 PM ----------
Because I'm rooted and unlocked I can edit the file... here is the contents of the file
# # OEM_BUILD_PROPERTIES #
ro.build.id=MPJ24.139-64
ro.build.version.incremental=65
ro.product.name=athene_amz
ro.mot.build.oem.product=athene_amz
ro.mot.build.customerid=amz
ro.carrier.oem=amz
so question... What does the CustomerID and Carrier.OEM need to be?
bigunwhistle said:
I'm wondering if changing that file will allow us to get on the correct upgrade path
---------- Post added at 02:31 PM ---------- Previous post was at 02:23 PM ----------
Because I'm rooted and unlocked I can edit the file... here is the contents of the file
# # OEM_BUILD_PROPERTIES #
ro.build.id=MPJ24.139-64
ro.build.version.incremental=65
ro.product.name=athene_amz
ro.mot.build.oem.product=athene_amz
ro.mot.build.customerid=amz
ro.carrier.oem=amz
so question... What does the CustomerID and Carrier.OEM need to be?
Click to expand...
Click to collapse
That's the main reason why I want copies of non-Amazon oem.prop files. I'd also like a few from different (primarily earlier) versions of stock ROMs.
I'm also interested in how you got the file to show up at all. I'm rooted and unlocked as well but I can't even see the contents of /oem without following the steps I posted.
MoseIlla said:
That's the main reason why I want copies of non-Amazon oem.prop files. I'd also like a few from different (primarily earlier) versions of stock ROMs.
I'm also interested in how you got the file to show up at all. I'm rooted and unlocked as well but I can't even see the contents of /oem without following the steps I posted.
Click to expand...
Click to collapse
I used solid explorer.
https://play.google.com/store/apps/details?id=pl.solidexplorer2&hl=en
#
# OEM_BUILD_PROPERTIES
#
ro.build.id=MPJ24.139-63
ro.build.version.incremental=64
ro.product.name=athene
ro.mot.build.oem.product=athene
ro.mot.build.customerid=retail
This is from a UK G4 xt1622, I ran CM and Lineage before downgrading to marshmallow. The last couple of Lineage made my WiFi unstable. I hope this helps.
Guys I have a problem I edited my oem.prop and now my phone will not make it past boot. It goes into TWRP and I can't get to that file again. Any suggestions? I can't follow the above directions because it will not allow me to mount OEM
bigunwhistle said:
Guys I have a problem I edited my oem.prop and now my phone will not make it past boot. It goes into TWRP and I can't get to that file again. Any suggestions? I can't follow the above directions because it will not allow me to mount OEM
Click to expand...
Click to collapse
Have you tried doing a factory reset and reflashing your ROM? Where exactly in the instructions I've provided are you getting stuck?
mikemelbrooks said:
#
# OEM_BUILD_PROPERTIES
#
ro.build.id=MPJ24.139-63
ro.build.version.incremental=64
ro.product.name=athene
ro.mot.build.oem.product=athene
ro.mot.build.customerid=retail
This is from a UK G4 xt1622, I ran CM and Lineage before downgrading to marshmallow. The last couple of Lineage made my WiFi unstable. I hope this helps.
Click to expand...
Click to collapse
Interesting, yours doesn't have "ro.carrier.oem" carrier property?
MoseIlla said:
Have you tried doing a factory reset and reflashing your ROM? Where exactly in the instructions I've provided are you getting stuck?
Click to expand...
Click to collapse
I have not done a factory reset yet or rom, does the rom overwrite the OEM folder? I have tried to restore my backup with TWRP and it is still not working. Also when I try do
ADB Devices the device is listed
when I goto ADB Shell and try to SU it says it isn't found (but it was rooted) and when I try to mount /OEM it says it can't find it in /proc/mounts
bigunwhistle said:
I have not done a factory reset yet or rom, does the rom overwrite the OEM folder? I have tried to restore my backup with TWRP and it is still not working. Also when I try do
ADB Devices the device is listed
when I goto ADB Shell and try to SU it says it isn't found (but it was rooted) and when I try to mount /OEM it says it can't find it in /proc/mounts
Click to expand...
Click to collapse
Follow the directions I've provided. If you skip even one of the steps you won't be able to make any changes.
As far as what happened to your install my GUESS is that your ROM is bugging out because that information is different from the original install. Are you using stock or something else?
MoseIlla said:
Follow the directions I've provided. If you skip even one of the steps you won't be able to make any changes.
As far as what happened to your install my GUESS is that your ROM is bugging out because that information is different from the original install. Are you using stock or something else?
Click to expand...
Click to collapse
I've got a 32gb amazon variant
the bootload it unlocked, system rooted TWRP installed and the ads disabled. Am I missing something. I'm running windows and I followed what commands you had listed but I still can't get it to connect.
MoseIlla said:
Interesting, yours doesn't have "ro.carrier.oem" carrier property?
Click to expand...
Click to collapse
Probably because the phone was bought unlocked, I E no carrier. In the UK you can buy most phones unlocked,and put in the sim of your choice, otherwise why have a dual sim phone?
bigunwhistle said:
I've got a 32gb amazon variant
the bootload it unlocked, system rooted TWRP installed and the ads disabled. Am I missing something. I'm running windows and I followed what commands you had listed but I still can't get it to connect.
Click to expand...
Click to collapse
I went back to pushed the soak test which allowed me to finally see the files in TWRP filemanager on the phone, renamed the backup I made of the OEM.PROP file to the correct name and rebooted, it worked!!! I have my phone back.... I had changed the last two lines from AMZ to retail it did not help.
mikemelbrooks said:
Probably because the phone was bought unlocked, I E no carrier. In the UK you can buy most phones unlocked,and put in the sim of your choice, otherwise why have a dual sim phone?
Click to expand...
Click to collapse
The Moto G4 is sold almost exclusively SIM unlocked to the best of my knowledge. Amazon being listed as the carrier must have to do with the way they deliver updates. Perhaps removing that line completely is what will set an Amazon device to retail on the update channel.
bigunwhistle said:
I went back to pushed the soak test which allowed me to finally see the files in TWRP filemanager on the phone, renamed the backup I made of the OEM.PROP file to the correct name and rebooted, it worked!!! I have my phone back.... I had changed the last two lines from AMZ to retail it did not help.
Click to expand...
Click to collapse
It's good to know that can happen. I'll play with it more soon. When I have the patience I'm going to downgrade and switch to some form of stock ROM.
MoseIlla said:
The Moto G4 is sold almost exclusively SIM unlocked to the best of my knowledge. Amazon being listed as the carrier must have to do with the way they deliver updates. Perhaps removing that line completely is what will set an Amazon device to retail on the update channel.
It's good to know that can happen. I'll play with it more soon. When I have the patience I'm going to downgrade and switch to some form of stock ROM.
Click to expand...
Click to collapse
I had to reroot the phone, I want to see that retail OEM.prop file really bad now... Do you think we need to make changes anywhere else?
bigunwhistle said:
I had to reroot the phone, I want to see that retail OEM.prop file really bad now... Do you think we need to make changes anywhere else?
Click to expand...
Click to collapse
If you look at the one mikemelbrooks posted it shows that there's no ro.carrier.oem property at all. Otherwise it's exactly what you did. My guess is just that the inconsistency is what was causing you issues, but I couldn't say otherwise. My oem.prop is modified and works fine under Lineage. You shouldn't modify your oem.prop unless you're planning on installing a ROM that's not compatible with the Amazon variant, so don't mess with it until you're going to attempt a flash which would necessarily involve a factory reset of your device.
MoseIlla said:
If you look at the one mikemelbrooks posted it shows that there's no ro.carrier.oem property at all. Otherwise it's exactly what you did. My guess is just that the inconsistency is what was causing you issues, but I couldn't say otherwise. My oem.prop is modified and works fine under Lineage. You shouldn't modify your oem.prop unless you're planning on installing a ROM that's not compatible with the Amazon variant, so don't mess with it until you're going to attempt a flash which would necessarily involve a factory reset of your device.
Click to expand...
Click to collapse
Yeah but his is a xt1622 I've been thinking about lineage is it the bees knees?
bigunwhistle said:
Yeah but his is a xt1622 I've been thinking about lineage is it the bees knees?
Click to expand...
Click to collapse
Cyanogenmod has always been a great ROM. I'm having some trouble with getting 4G(I only get 3G) but I don't think my problem is typical. I'm on a Sprint-based MVNO so that may have something to do with it. I would recommend backing up your current install and giving it a try.
Introducing:
SamFAIL!
[Size=DEPRECATED]DEPRECATED![/size]
This ENTIRE THREAD is old, busted, and has been deprecated for some time. Please stop reading it, and go to the link below this line of text:
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
It has some very clear advantages over this version:
- Supports All existing bootloader revisions
- Latest version(s) of Nougat
- Huge community of support
- Telegram channel
- Preinstalled audio mods, visual mods, looks really good
- Actually still works
- very debloated without compromising many touchwiz features. It's over 50% faster on my device
- Deodexed, xposed FULLY supported.
- Rooting method improved, essentially foolproof
I don't want to have this thread closed, but I will
A New Alternative Root Method For The US Samsung Galaxy S8! (G950U Snapdragons)
Rooting your s8 just got easier.
DISCLAIMER 1: Although this method does not trip the "Knox Flag" you are still taking a risk by rooting your device. We are not responsible for your blazing fast smartphone with root! Let's hope this one doesn't catch on fire!
DISCLAIMER 1.5: THIS IS NOT FOR EXYNOS!
First and foremost, SHOUTOUTS!
- @partcyborg for finding the root method!
- @me2151 for testing on Note 8 and facilitating root on the Note 8!
- @elliwigy for... Shenanigans! And thread template
- @Chainfire For opening the door to make this root useful. He will be missed! (no he is not dead, just retired.)
- @samsung for the amazing phone and leaving rediculous loopholes open for us to root!
Disclaimer 2: The method to root should be pretty straight forward as the hard work has already been done for you. With that being said, you will need to know how to download files from the internet, extract a zip file and to use ODIN. That is basically it! Oh yea, PLEASE BE SURE TO READ ALL THE INSTRUCTIONS THOROUGHLY BEFORE ASKING FOR HELP!
Once again...
READ THE ENTIRE SET OF INSTRUCTIOMNS BEFORE BEGINNING!
There are important things to note about this process that WILL likely trip you up if you expecting them. Some things are not intuitive and may sound unimportant to follow but trust me they are. Every single step added her is absolutely necessary.
Prerequisites:
- A working computer with a working USB drive that is capable of successfully flashing firmware to your device.
- Comsey ODIN and Normal ODIN (Found in Post #2 As well)(In case you give up and want to go back to stock)
- SamFAIL S8 Custom Hybrid Combo/Stock firmware package (also in Post #2)
- A functioning Snapdragon Galaxy S8 G950U/U1 or ANY other US Snapdragon based Galaxy S8 that can run the standard 950U firmware. Must be able to boot to download mode, and NO EXYNOS OR
- The CSC file for your phone(also in Post #2)(NOTE: You MUST use the CSC matching your device or your network will not function correctly. If your CSC is not in the downloads section you must download your devices firmware and extract the CSC from it and use that one. I will continue to add CSCs as I have time to download them but please be patient as they can take a while to download. Bonus points if you can send me individual .tar.md5 CSC archives so I don't have to download 4GB of ROM.
Part 1 Instructions:
0) BACKUP YOUR CRAP This procedure wipes your entire phone, so anything that you don't want gone for good back up somewhere NOT ON THE PHONE for the duration of this process. TECHNICALLY it should be safe to leave on a SD card, but checking one accidental checkbox in Odin will make you lose it. Take the SDCard out or copy the stuff to your computer.
1) Unzip the SamFAIL S8 ZIP archive. Inside there will be two tarballs (.tar files). If you have flashed a rom before these should hopefully look familiar. NOTE: There is no CP archive because the hybrid BL_ archive contains all drivers needed to operate your device.
2) Boot up Comsy Odin. Reboot your phone into download mode. Connect your phone to your pc and make sure that you get the Blue box that signifies proper connectivity and that the Odin log has said "Added!"
3) In the AP slot, place the AP tarball. There will not be a long pause like stock ROMs as there is no md5 signature to check.
4) In the BL slot, place the hybrid combo/stock firmware package. Again, you can place these in any slot and Odin will handle it just fine.
5) Click on the OPTIONS tab, and select the following checkboxes: Auto Reboot, Re Partition, F. Reset Time, NAND ERASE ALL.
After finishing the above steps, your Odin should look exactly like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6) Read step #5 again and confirm that you have everything selected EXACTLY as shown in the picture and written in the words. Check it again and when you are sure everything is correct press START.
7) Wait for ODIN to complete the flashing of the system partition. Naturally, ODIN and your phone will see this image is not signed and return FAIL. Your device will say "Secure Check Fail: system" or something close to it. THIS IS EXPECTED, DO NOT PANIC OR GIVE UP. Your flash may have failed, but it did not fail hard enough
At this point you may be wondering "What is going on and how does failing to flash get me root?"
The answer is because of a very simople to fix (pre-launch) issue with secure boot verification. I will explain in more detail when we are done and you have root but the short story is, yes they fail the flash when it does not match a known image, but they do so at the end, AFTER all of the data has been written to the disk!
it indicates that everything is ruined and you should bring them your phone right away. Fortunately we are smarer than that. Despite not saying so, while this screen is showing the device is in fact in download mode ready to receive new firmware.
This screen will likely say something like "System Failure" and there will be instructions displayed to take your device to the nearest repair store. Laugh at Samsung's silly attempt at subterfuge.
Now, lets put that data to good use with part II:
8) Reboot the phone into download mode again (hold down power, vol down, bixby) until the device resets back to a blue-green ("Download Mode Color") screen. If you have not seen or experienced a bad flash before, this screen may be new to you. You should see something that says "OPERATING SYSTEM UPDATE FAILED" and find that your phone will boot only to this state and nothing else. DO NOT PANIC! THIS IS EXPECTED and exactly what we want. Odin/Secure Boot are refusing to boot because you flashed unrecognized code, and wants you to flash code it recognizes. Lets give them what they want.
9) If you closed Odin or hit Reset after the first clash, open it again. Plug your phone back in if necessary and ensure that Odin sees you device just like last time.
10) IMPORTANT! IMPORTANT! It is IMPORTANT that you be sure to remember to do the following: Click the RESET button onthe bottom middle of the page. Alternatively, you can Uncheck "NAND Erase All" "Re-Partition", but its extra work to remember which ones.
WARNING: IF you fail to do this, Odin will happily erase your device and have to start from scratch. Worse though is the failure mode. If you don't notice is not obvious that it is caused by this, which will likely cause you and others unecessary grief.
11) Click on the BL row again and Load the same Hybrid Firmware Combination as last time. Be sure the checkbox next to it is selcted.
12) IMPORTANT: If you did not click "Reset", be sure that the AP_ROOTEED_YSTEM tar is NOT loaded. You can uncheck the check box next to it and it will not be sent as part of the coming flash. If you do not do this, you will fail again and it will be for real this time.
13) Click on the CSC row and load the CSC file you downloaded that matches your device and service plan. Be sure that the checkbox next to it is checked.
14) Double check that your screen and options now look like this or has the same options.
- NAND ERASE is UNCHECKED
- F RESET is CHECKED
- REBOOT is CHECKED
This part is basic ODIN flashing here guys... Not rocket science!
15) Press START and watch the LOG tab to see what is happening. If it says the words "Erasing..." you have failed to follow directions and ust start completely over with step again.
16) This is where the Matic happens... Odin will flash all of the fimrware files in the tarball, and will fihnd that all of them are 100% valid signed images by Samsung. Since Odin has a very poor memory, he completely forgets that you had just flashed a bad system image, and marks your secure boot flag as "Safe" and lets you proceed to boot!
17) Have a good laugh (at least i found if funny)
18) The phone will reboot to recovery and dump you there for one of two reasons:
a) You will see the progress bar advance over a feconds to 32% or so and then stop, printing an error about faling to find resize data. This is normal and happens with every flash of CSC OYN that I have ever seen. You are safe to advance to the nxt step.
b) The recovery will immediately exit with an error that says "Failed to mount /system (Invalid Argument)". This is unfortunately bad news as it means that the failed flash attempt was not successful in writing enough data to see the file system. Do not dispair yet though! This happens sometimes with this method. Start off by starting over from scratch. If that does not work, reach out to me and I will walk you through a few procedures that will eventually fix it.
19) If you made it past step 18, all you need to do now is execute a data wipe/factory reset. This is necessary and your device will not boot withiout it, as there is no userdata image file flashed through odin.
Now, wait for the device to boot up (it will take 3-5min like most new isntalls) and then you can try out your new root!
20) Once phone boots up, Setup your device as normal and proceed to the SuperSU app. It will ask you to update the SU Binary. Select Normal method and let it do its thing. A popup should show up to disable KNOX. Follow its instructions then SU should say it was Successful in updating and it needs to reboot(You may have to do it multiple times. I belive its 2 or 3 times then its good) ENJOY SamFAIL ROOT!
NECESARY CLEANUP
The reason that this works at all is that modern filesystems like ext4 (what android uses) are very robust in the face of errors on the disks. Particularly in the days of old when everything was on spinning platters, that may moving parts was a lot more prone to failure, so filesystems were designed to keep your data safe in the face of losing parts of the disk. Fortunately for us this allos us to successfully mount and load android off of an incompleted filesystem. To make sure that the device is table, and that future SamFAIL attmpts do not degrade into "Invalid Argument" errors, we need to do a filesystem repair.
Download fsck.ext4 and push it to your device to fix any errors that cropped up from the SamFail dirty flash.
Connect via adb (or shell on your device) and run the following
FROM YOUR COMPUTER WITH PHONE PLUGGED IN AND AD ENABLED:
Code:
adb push <localpath to fsck.ext4 /tmp/
Then on the Device:
Code:
su
chmod 755 /tmp/fsck.ext4
mount -o ro,remount /system
/tmp/fsck.ext4i -f $(find /dev -name system)
It is possible that oyu will see a LOT of errors reported. Do not worry though all of the stock os will have made it through ok. Press "a" to say auto-yes to all the questions and your filesystem will be healthy from here on out.
EPILOGUE
It is HIGHLY recommended that you follow this step with the flashing of either a custom rom or a full stock /system ROM using FlashFire. The image I provided that is pre-rooted essentially has no more work done to it than that, and I have no plans to do that work anytime soon. Unforutnately my experiments with using SamFAIL to flash more custom /system partitiuons made them a lot more unstable and frequently would not boot at all. Consider this a stepping stone that requires a little less work than SamPWND used to be before more automation work was done.
The AQH3 Image in post #2 has the "warning this device has been modded" message and i took a brief stab at it but wasnt able to get it locked down. If someone wants to do so i will havppily upgrade the rom to a better vesrion. Otherwise there are some really cool bnew roms out for the s8/s8+ now that I recommend checking out.
The more exciting prospect is that this can be used by ANY Samsung device with a permissive Selinux version without dm-verity. That covers a wide range of devices which we will be investifating.
DISCLAIMER 3:
* SamFAIL DOES NOT TRIP KNOX
* SamFAIL DOES NOT FIX THE 80% BATTERY CHARGE ISSUE
* Boot.img is SECURE which means you MUST use SYSTEM ROOT. (Similar to SamPWND)
* This means that MAGISK DOES NOT WORK
* Which also means SAFETY NET FAILS. So any apps you enjoy that require passing Safety Net will most likely not work while you are rooted with SamFAIL
* Again, similar to SamPWND, this root method uses a factory binary boot.img which is necessary to boot the modified system. THIS MEANS BATTERY ONLY CHARGES TO 80% (Thanks Samsung.)
* SamFAIL DOES NOT UNLOCK YOUR BOOTLOADER AND DOES NOT SIM UNLOCK YOUR PHONE.
* This *should* in theory, work for other Snapdragon Models of the Note 8. If you have another model and are successful please post so we can add "support" for other models.
Back to Stock?
- Download the full STOCK firmware of your choice.
- Flash it in ODIN/Comsey ODIN as you would any other time!
- It will take a few reboots for the "custom" splash screen to go away.
Donations:
As always, the devs have been hard at work recently to bring you root. Donations are definitely NOT REQUIRED but if you feel generous and want to spot the devs a few bucks for their hard work you can donate to this Paypal Address:
Donations
NOTE: this message is geared more towards the Note 8 users, for whom this root method is their first and only.
DOWNLOADS will be in POST #2
UPDATES will be in POST #3(RESERVED FOR FUTURE UPDATES)
As always, ENJOY ROOT and thank SamFAIL for making it all possible!
P.S. See why we called it SamFAIL now? Massive fail on Samsungs part.
SamFAIL Downloads
Rooted AQH3 Android 7.0 System for Galaxy S8 Snapdragon (Flashing in Odin)
AP_SamFAIL_G950U1_AQH3_ROOTED_SYSTEM.tar:
Hybrid Stock/Combination Full Firmware (minus userdata and system) For Rooted Devices.
AQI6 Stock, AQI1 Combo (for Flashing in Odin):
BL_SamFAIL_G950U1_HYBRID_AQI6_STOCK_AQI1_COMBOtar.tar
VZW CSC OYN for US VZW Customers on AQH3 (for Flashing in Odin):
CSC_OYM_SamFAIL_G950U1_AQH3_VZW.tar.md5
Staticly Compiled fsck.ext4 binary for fixing filesystem issues:
fsck.ext4
*YANK*
(reserved for future use)
Yay!
Nice!
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
i have 1 or 2 but not gonna upload em until theres more stuff done.. its basically got minor visual mods and deodex n theusual stuff
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Click to expand...
Click to collapse
but yea,just not enough done yet in order to release.. i hope note 8 root will kick offmore mods n such for us
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
partcyborg said:
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
Click to expand...
Click to collapse
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Click to expand...
Click to collapse
Aww that's a bummer, last I talked to him he was fine with other carrier use.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
all he has to do is flash a csc after the rom lol if all he did was remove the other carrier stuff
Will this work for the S8 Plus?
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
elliwigy said:
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
Click to expand...
Click to collapse
I'm going to do my best to make one shortly but given I do not have an s8+ to test on I'm not so sure how effective I will be
Does this work? Anyone tried. I really want to root my Canadian model sm-g950w
Ad.Shk2 said:
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Click to expand...
Click to collapse
I think the usual comment about camera quality degrading still stands when using AOSP ROMs? Have yet to root the Samsung S8 but I'd like to do it soon, along with flashing a debloated ROM for my sister.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
His rom has all the carrier info in it. He just doesn't update the op except the link to new rom.
Avoid and pass by a fool and a madman
Great effort! thank you very much.
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
jaygan93 said:
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
Click to expand...
Click to collapse
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
wga0 said:
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
Click to expand...
Click to collapse
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
jaygan93 said:
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
Click to expand...
Click to collapse
I'd tried them also, and they also generated some images corrupted when using on Black shark ota. I tried almost payload_dumper I could find at internet, only one, payload_dumper-master for incremental has the needed operation for full payload, and no one worked for incremental.
MCT_ said:
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
Click to expand...
Click to collapse
I can't understand your word exactly, but the system never do lock/unlock during update. And... why are you talking that here? It has nothing to do with this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
MCT_ said:
View attachment 5008907
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
Click to expand...
Click to collapse
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
wga0 said:
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
Click to expand...
Click to collapse
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
MCT_ said:
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
Click to expand...
Click to collapse
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
wga0 said:
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
Click to expand...
Click to collapse
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
MCT_ said:
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
Click to expand...
Click to collapse
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This code is just a ".cmd " project and some draft entries from the "one-click" flashing engine using ADB.
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
KM7 said:
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
Click to expand...
Click to collapse
When you get root, via /data/media/... there is a dependency of the partition with internal storage, but you do not mention this and suggest using flash in its various variations. :good:
I don't even have a development section:
My bootloader is closed, I'm waiting for an update.
I've tried everything here, from bs2pro firmware on bs2 to payload_dumper and update.
With Google's floating code, this won't work, or you'll end up in the stone age.
Code is constantly moving.
You must obtain superuser rights legally, via the server.
Why do you need ROOT if you don't have a BootLoader, Recovery and ROM ?
What would delete installation APKs from system/app without disabling services ?
You made a copy of the system in img format for two months, with ROOT license on Board.
wga0 said:
EDIT: I found that more images in the full Android 10 OTA are corrupted when extracted with the payload_dumper, even including the boot image and modem.img, which is critically related to boot. I write this urgently... and will update soon... (Plz use with REPLACE part, or with below modified code)
Please be careful when you use the payload_dumper for full payload.
I found the payload_dumper doesn't have all the operations needed. It supports only two operations, REPLACE_XZ(lzma compression), REPLACE_BZ(bz2 compression), but BlackShark full OTA requires REPLACE(no compression, bsdiff or other format) also, and it generates some images incorrectly. It doesn't show you an error or any sign of malfunction also.
It seems that using it for the boot image only is okay, but images such as vendor.img, system.img are not correctly generated and it can brick your phone.
You can use payload_dumper-master instead. It supports the REPLACE operation for full payload, although it requires the vc++14.0 to compile the bsdiff library. I think easy way is to copy the REPLACE part in payload_dumper-master to payload_dumper, and use that.
Or you can modify the boot_extractor I uploaded to extract all files. Just delete the search part (comparing partition name), then it will extract all images.
oh... you need to change one more part...
Code:
#SOURCE_BSDIFF for Black Shark
elif op.type == op.REPLACE:
if pat[:3] == b'BSD':
odata = bytes()
for ext in op.src_extents:
ofile.seek(ext.start_block*block_size)
odata += ofile.read(ext.num_blocks*block_size)
pat = bsdiff4.patch(odata,pat)
ndata = io.BytesIO(pat)
for ext in op.dst_extents:
nfile.seek(ext.start_block*block_size)
nfile.write( ndata.read(ext.num_blocks*block_size) )
This will work for all images, all OTA for other phones (universally), and for both full, incremental of course.
Click to expand...
Click to collapse
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
abd96iq said:
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
Click to expand...
Click to collapse
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
KM7 said:
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
Click to expand...
Click to collapse
I tried but unfortunately doesn't work bro
I have even contacted s-unlock team but to avail
I think i will throw it in trash .
I am really sad
Thank you bro
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?