Related
I've been searching for a straight forward up to date guide but have failed. So I'm hoping to find a way that works and spread the info around in detail.
INFO:
Model: SM-G900A
Baseband: G900AUCU2AOA2
Kernel: 3.4.0-3116194
Not sure if the security enhancements have an effect.
I've tried Towelroot bUT not supported even when at 4.4.2
One-click-root seems like a scam, does say it's rootable but with no post about success only failure not about to waste S40.
Also why doesn't towelroot work? I tried it the second I got my phone so I took the update to 4.4.4. Well not by choice. It started the install when i was sleeping... Not cool Do I have to use Odin to flash to NCE?
So please help, I want to get this rooted before it updates to 5.0 without my approval
You can't, needed to be rooted on KK, if you took the official update you're SOL
Sent from my Tw5ted SM-G900A using Tapatalk
This exact same thing happened to me despite the fact that I thought that I had frozen the updates. I was able to root OA2 and prevent updating to 5.0, though. Here's how I did it.
Basically, just follow this guide: http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
Even though I was on OA2, flashing down to ND3 via Odin and then running Towelroot anyway successfully rooted my phone. I couldn't find the OA2 kernel at the time, so I just flashed up to the OA1 kernel instead (yes, alongside the OA2 basebands) and didn't see any problems with it. I am still using the OA1 kernel this way now.
I don't know if there is anything actually different between the OA1 and OA2 kernel, but I have been running with this configuration for about a month and a half with no real problems -- but your mileage may vary. (Your phone may burst into flames and start chanting versus from the Necronomicon. You have been warned.)
While I'm still on the OA1 kernel, I happened to do a quick search and found the OA2 kernel floating around here: https://www.androidfilehost.com/?fid=24052804347799283 -- but flashing this thing is not something that I have personally tried (although now I am tempted to).
So if you do flash this one, good luck -- but again, I can't be held responsible for any damage to your phone (or psyche, in the event of demonic possession).
I've tried those instructions but when I tried flashing in odin it froze at boot.img forcing me to power off my cell. Luckily it didn't affect anything. I was surprised about the size of the file only being around 10Mbs and that the link takes you to the S4 files section. I'll try it again tomorrow to see if it works this time.
Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.
*kernel. Damn voice to text.
That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.
Got one recently too. Would also appreciate any more information on rooting.
I have a J320A (AT&T) came stock with 6.0.1, can help test if needed
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez
Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!
Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Hey,
Check for a pre-rooted firmware for your version available on XDA then flash it using Odin.
There are lot of tutorials to root this model over there.
brbninjaa said:
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Click to expand...
Click to collapse
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
MelonChickens said:
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
Click to expand...
Click to collapse
I have also tried (and disliked) one of those pre-rooted firmwares; it is a pity that all there is available for this device are a couple of outdated and bloated versions. I even tried to build my own firmware, but failed to create anything bootable (fortunately, I managed to not brick my device).
Then I tried the TWRP route: following a couple of guides I found here, I managed to install it, and use it to install the latest SuperSU .zip file. TWRP reported no errors, and everything seemed correct, but when the device boots there is no trace of any rooting: no SuperSU app, no "su" binary, no nothing at all...
Thus, if you could post here how you managed to make this work, I would be very grateful.
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Atronid said:
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Click to expand...
Click to collapse
Right on.
eduardo.perezesteban said:
I have also tried (and disliked) one of those pre-rooted firmwares; it is a pity that all there is available for this device are a couple of outdated and bloated versions. I even tried to build my own firmware, but failed to create anything bootable (fortunately, I managed to not brick my device).
Then I tried the TWRP route: following a couple of guides I found here, I managed to install it, and use it to install the latest SuperSU .zip file. TWRP reported no errors, and everything seemed correct, but when the device boots there is no trace of any rooting: no SuperSU app, no "su" binary, no nothing at all...
Thus, if you could post here how you managed to make this work, I would be very grateful.
Click to expand...
Click to collapse
Well, first I installed TWRP 3.0.2.0 also using the guide somewhere in the forums, then I downloaded SuperSU 2.46 .zip from the Chainfire website and flashed it using TWRP.
If the SuperSU .zip file didn't work for you, then try CF-Autoroot, whatever that is. I don't know because I have not tried it on my phone. I believe that it finds exploits and uses them somehow?
Anyway, did you flash the ZIP without extracting it? I don't see how it can't work, really. Call me stupid, but I don't know why that happened.
Anyways, good luck to all, for I am not active on these forums nowadays (as much)
MelonChickens said:
Well, first I installed TWRP 3.0.2.0 also using the guide somewhere in the forums, then I downloaded SuperSU 2.46 .zip from the Chainfire website and flashed it using TWRP.
If the SuperSU .zip file didn't work for you, then try CF-Autoroot, whatever that is. I don't know because I have not tried it on my phone. I believe that it finds exploits and uses them somehow?
Anyway, did you flash the ZIP without extracting it? I don't see how it can't work, really. Call me stupid, but I don't know why that happened.
Anyways, good luck to all, for I am not active on these forums nowadays (as much)
Click to expand...
Click to collapse
Same TWRP version, same SuperSU version, did not extract the ZIP file. It took me several attempts, but I finally managed to install TWRP and "install" SuperSU without errors. I do not doubt it worked for you, perhaps my base ROM is different, and has some type of protection that deletes any "su" file.
Will have a look to CF-Autoroot, thanks for the tip!
---------- Post added at 08:46 PM ---------- Previous post was at 08:39 PM ----------
CF-Autoroot website looked very promising, I could select a recent ROM and configure it, but the build process produced an error:
Code:
Current status: ERROR
Estimated wait: NOT APPLICABLE
Will keep investigating.
Atronid said:
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Click to expand...
Click to collapse
As promised I re-uploaded the original version (without bloats) of the firmware. Check this: https://forum.xda-developers.com/ga...odified-pre-rooted-firmware-sm-g361f-t3693589
MelonChickens said:
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
Click to expand...
Click to collapse
I flashed that same firmware before and I had the same issues. Had to download my original firmware from some site with terrible download speeds, took forever. Nice to know you found an alternative and I'm sure I would find more cool things to do with root.
brbninjaa said:
I flashed that same firmware before and I had the same issues. Had to download my original firmware from some site with terrible download speeds, took forever. Nice to know you found an alternative and I'm sure I would find more cool things to do with root.
Click to expand...
Click to collapse
So, just wondering, but I like to wrap things neatly;
Have you managed to root your device or are you still trying?
brbninjaa said:
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Click to expand...
Click to collapse
I just need the root because I have to retrieve attachments whatsapp that I deleted by mistake on the internal memory. as the software with which I should recover (dr fone) fails to do the root.
There is very little here on rooting that isn't fairly old, most of the methods use tools which have been updated or are no longer applicable because of updates to the stock firmware and evolving methodology. For this reason I thought I would get a data point out there about rooting with magisk. This is only one way and won't be suitable for all users but it works for those who like me are picking up this device on sale as it reaches end of life and want root.
With that said here is what I did... I let the tablet update itself to the latest possible firmware which put it on a USA variant of 7.0, I found the exact version of the installed firmware and downloaded it to my PC. I installed the magisk app on the tablet. With those things set up I unzipped the firmware and snagged the boot image. I transferred that to the tablet and let magisk make a modified boot image. I then transferred that back to the PC and flashed it with Odin. A person could also do this with fastboot but I don't my laptop set up for it making Odin the go to choice.
Worked fine and the tablet is rooted. Keep in mind this is root only solution. I find I only use my tablets for media consumption so I don't care about having a custom recovery as I don't need to make any significant changes. A person should peruse the magisk thread opening page to get detail instructions and there are a number of YouTube videos showing the process for those that haven't fiddled with this stuff before. Do remember you will need to adjust the settings in magisk depending on whether you're going to go Odin or fastboot.
Bottom line, it worked fine.
This method will trip the knox counter?
Thanks!
krabman said:
There is very little here on rooting that isn't fairly old, most of the methods use tools which have been updated or are no longer applicable because of updates to the stock firmware and evolving methodology. For this reason I thought I would get a data point out there about rooting with magisk. This is only one way and won't be suitable for all users but it works for those who like me are picking up this device on sale as it reaches end of life and want root.
With that said here is what I did... I let the tablet update itself to the latest possible firmware which put it on a USA variant of 7.0, I found the exact version of the installed firmware and downloaded it to my PC. I installed the magisk app on the tablet. With those things set up I unzipped the firmware and snagged the boot image. I transferred that to the tablet and let magisk make a modified boot image. I then transferred that back to the PC and flashed it with Odin. A person could also do this with fastboot but I don't my laptop set up for it making Odin the go to choice.
Worked fine and the tablet is rooted. Keep in mind this is root only solution. I find I only use my tablets for media consumption so I don't care about having a custom recovery as I don't need to make any significant changes. A person should peruse the magisk thread opening page to get detail instructions and there are a number of YouTube videos showing the process for those that haven't fiddled with this stuff before. Do remember you will need to adjust the settings in magisk depending on whether you're going to go Odin or fastboot.
Bottom line, it worked fine.
Click to expand...
Click to collapse
My friend are you able to tell me if you are able to root t713 with latest androind update, which is NRD90M.T713XXU2BRB2.
Please be so kind and let me know.
Thx
netgar said:
My friend are you able to tell me if you are able to root t713 with latest androind update, which is NRD90M.T713XXU2BRB2.
Please be so kind and let me know.
Thx
Click to expand...
Click to collapse
Fortune has it that my installed firmware is exactly that so I'm going to go with a yes on that.
krabman said:
Fortune has it that my installed firmware is exactly that so I'm going to go with a yes on that.
Click to expand...
Click to collapse
Thank you but Im going to root it using SU and flash TWRP. As I can see you just modified boot img and flashed magisk.
Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?
I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
milesius said:
Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?
Click to expand...
Click to collapse
teeterteeter said:
I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
Click to expand...
Click to collapse
I modified the oem.prop file on the update image by adding AMZ to the athene names. I will upload that here when I get a chance. I haven't actually tried this because my bootloader is locked and I cant wipe this phone as I use it for work.
I flashed Stock Oreo 8.1 OPJ28.111-22. Very slow.
Tried both ElementalX and loonykernel with magisk root, slow, lots of changes... still slow. Whole interface lags. Very slow!
Removed moto apps, still slow.
IDK what else to remove or change...
Trying now again (full wipe and flash) but I'm going back to Nougat Stock after this.