Related
Sooo I recently purchased this device and it is a nice lil budget phone with amazing battery life. I am reallllly hoping others are out there with this sucker and savvy enough to work together on rooting this device and possibly more customization later on down the road afterwards. I have the Cricket Variant LGK450 and so far getting into fastboot is a no go and I am basically stuck until root is gained on this device as I am guessing everyone else with it is as well. So this thread is basically for things you have tried to gain root on the device and sharing information on what has worked and what hasn't for you and any other tips and tricks you have discovered using this device any info could be helpful until we perhaps get an official thread in the LG Forums like the X Screen and X Cam have. So far the only thing I have really gotten into to do some tinkering with is using the dialer code *#LGMENU#*450# and you can modify various things there and some of the more useful tools for logging are there as well, and crash handler/ramdump etc. running a ls -l -R | grep -E "^c.{6}((r.)|(.w))" in shell shows that the only drivers we could mess with are as follows.
crw-rw-r-- system radio 10, 55 2016-01-01 08:32 alarm
crw-rw-rw- root root 10, 60 2016-01-01 08:32 ashmem
crw-rw-rw- root root 10, 61 2016-01-01 08:32 binder
crw-rw-r-- system system 10, 95 2016-01-01 08:32 ion
crw-rw-rw- system system 240, 0 2016-10-04 23:53 kgsl-3d0
crw-rw-rw- root root 1, 3 2016-01-01 08:32 null
crw-rw-rw- root root 5, 2 2016-10-04 23:53 ptmx
crw-rw-rw- root root 1, 8 2016-01-01 08:32 random
crw-rw-rw- root root 5, 0 2016-01-01 08:32 tty
crw-rw-rw- root root 1, 9 2016-01-01 08:32 urandom
crw-r--r-- root root 10, 53 2016-01-01 08:32 xt_qtaguid
crw-rw-rw- root root 1, 5 2016-01-01 08:32 zero
crw-rw-rw- root root 1, 3 1969-12-31 18:00 null
Everything else is permission denied.
I am also interested in this. I haven't got far at all. This is a great value phone so i am really hoping someone can root it.
I am wondering if we could compile this exploit and give it a try i tried to compile it with gcc but it threw a ton of errors but if someone else can put this together I will test it please check out the following exploit code https://www.exploit-db.com/exploits/39340/ We do indeed have sensord service and it is running as root so in theory this exploit should work on our device I think but I need someone to help me out with how I would compile it I have metasploit and such but i am pretty new to messing around in there I am running Kali Linux x64 my guess is that I am compiling it incorrectly.
Have a LG xpower android 6.0.1, tried many ways/online tutorial, can't root it
I have checked the connectivity by "adb devices".
After run command "adb reboot bootloader", LG Xpower then go to "fastboot mode". The screen is black and "=> FASTBOOT mode..." is shown at the left bottom corner.
However, after that, the PC was failed to recognize it.
I opened device manager and realised under the section "Other device" with an unsuccessfully installed device(unrecognized character). I have verified that is the LG Xpower by unplug and plug the USB cable.
I got stuck here.
Although Xpower can be in FASTBOOT mode but the PC cannot recognize it. Depressed.
I am new here and don't know how to post the screen capture image.
What provider do you have? I have cricket and no fastboot for me at all you would seem to at least have hope sounds like your just missing some drivers.
I am wondering guys I think what I have dug out of the device may be good news but wanted to get feedback on if yall think it would work or not, I got the otacerts.zip off of the device and within is releasekey.x509.pem which is the same key used to sign the OTA updates and they must match that key in order to pass and flash to the device sooooo if I was to make a prerooted system for instance and sign with this pem could I actually flash that to the device without a brick?
could anyone provide a link to a stock spft backup please!!
new root?
is there anyone who rooted the lg x power?
Well you could try the latest KingRoot I no longer have this device swapped to a s5 then also got me a moto g4 to tinker with. I would say best chance is kingroot.
KazuDante said:
could anyone provide a link to a stock spft backup please!!
Click to expand...
Click to collapse
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
t5678 said:
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
Click to expand...
Click to collapse
To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say for are but I had done that on mine also the main prob is the security updates that's what will kill chances of rooting so don't take those if you can help it and I think some models like boost maybe if your able to get to fastboot then you should be able to unlock the bootloader then build a tarp or cwm recovery flash a systemless root and then custom Roms etc but for most if you can't get to fastboot like the attached or cricket variant then you will most likely have to wait til kingroot figures something out
toxinburn said:
To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say for are but I had done that on mine also the main prob is the security updates that's what will kill chances of rooting so don't take those if you can help it and I think some models like boost maybe if your able to get to fastboot then you should be able to unlock the bootloader then build a tarp or cwm recovery flash a systemless root and then custom Roms etc but for most if you can't get to fastboot like the attached or cricket variant then you will most likely have to wait til kingroot figures something out
Click to expand...
Click to collapse
Thanks for the info on question 2).
Also thanks for the security update warning. Do you know if "com.lge.bnr" was the type of security update that makes rooting harder? If anyone can confirm, then future new owners can be quicker to disable it before the update is forced.
So for question 1), you are saying that for me to make a CWM backup, that I WILL have to unlock bootloader somehow?
If possible, I wanted to make a CWM backup without any risky flashing, in case a problem occurs - since if a problem does occur during flashing then I wouldnt have a backup to install lol.
But if someone tells me it is low risk, and the current method works on this new device, then ill try to get an original CWM backup for the rest of us to have as backup.
t5678 said:
Thanks for the info on question 2).
Also thanks for the security update warning. Do you know if "com.lge.bnr" was the type of security update that makes rooting harder? If anyone can confirm, then future new owners can be quicker to disable it before the update is forced.
So for question 1), you are saying that for me to make a CWM backup, that I WILL have to unlock bootloader somehow?
If possible, I wanted to make a CWM backup without any risky flashing, in case a problem occurs - since if a problem does occur during flashing then I wouldnt have a backup to install lol.
But if someone tells me it is low risk, and the current method works on this new device, then ill try to get an original CWM backup for the rest of us to have as backup.
Click to expand...
Click to collapse
Well the only way to get a CWM backup or TWRP backup would be to first unlock the bootloader on the device, but since you can't get into fastboot to actually unlock the bootloader their is no safe way to flash a CWM or TWRP nor is their a custom recovery compiled for this device, you cant just flash any twrp or cwm build and expect it to function since they need to be compiled for each device independently in other words the CWM and TWRP are device specific and when you build either one you have to specify which partitions the specific device your building for is using for various things such as the system and boot etc. And these partitions vary from device to device, I am not sure what the app does that updated either, but for sure do not try to flash twrp or cwm unless it has been built for your specific device and you wont ever be able to without an unlocked bootloader since 6.0 uses dm verity etc if you flash custom recovery or rom to this device without the unlock in effect it will most likely soft brick at the very least. In the past their were ways to kind of sideload roms from the external sd card but that from what I know of is no longer an option unless someone figures out a new way to bypass the newer security checks, I am not going to say they never ever will but it will take some time at the very least....From all the times I have messed with rooting and customizations on android through the years I would say your safest bet in the future is to make an educated purchase before you decide to buy a new phone if you for sure want to be able to root and use custom anything like roms and kernels then you need to find out beforehand is your device going to support bootloader unlocking officially or is their already an exploit that will enable you to do so in existence at time of purchase, I find if the unlock is not supported officially then you would probably want to get a flagship device as the devs and exploit gurus typically work it out on those devices first and steer clear of ATT devices or Cricket as they rarely get the support from the community for things of this nature due to the total lockdown methods att seems to use on their devices in the past years to present. I would recommend HTC or Motorola as they seem to support unlocking officially on many more devices than other manufacturers and even still you may have to buy them directly from them vs the carrier as the carrier has the option most of the time to lock the bootloaders and customize the roms the way they want with all the bloatware etc. T-Mobile is also usually unlocked as well or at least easier to figure out a way to get unlocked vs ATT or Verizon, I am not sure about some of the smaller carriers but I think Metro PCS also has alot of devices that you can get unlocked fairly easy. I hope this sort of enlightens you to what exactly your asking for and educates you a little more for future reference. I am using Cricket as my carrier due to the cheaper price, no contracts and they use ATT towers which seem to have best reception in my area but their devices suck if you want to root and unlock the bootloader as they use the same firmware as the ATT phones and those too are mostly locked tight and most of them you cannot even get into the stock recovery without a no command message which does you no good at all, so I mostly order my devices from the net directly from the manufacturers and inquire beforehand on whether or not they support bootloader unlocking on them, or you can find good deals on swappa.com or sometimes ebay just make sure they are the right variant of the device your wanting, because sometimes you for instance have the LG X Power which on Cricket you cannot even get to Fastboot to even try to unlock the bootloader but on T-Mobile their variant probably would allow you to access it, the device would also be called LG X Power but the actual variant number would be different so you really gotta check all those things first. I really wanted to dev for this device too, but I quickly noticed that the chances of someone getting the thing unlocked were slim to none therefore I decided to move on. It is sad as the X Power does have some great potential to be made alot better with a custom kernel etc. but their is nobody with the knowledge needed really working on it at this time that I know of.
"they need to be compiled for each device independently"
So even if two people have the exact carrier model number, the CWM backup for one phone will not work for another phone (with a different MEID)?
I was trying to help give a CWM backup for people who have my carrier model phone, since I havent done the extra updates. But if its not possible...
"you wont ever be able to without an unlocked bootloader since 6.0 uses dm verity etc if you flash custom recovery or rom to this device without the unlock in effect."
So the downgrade to a lower android, then root, then update, doesnt work anymore (due to dm verity that prevents downgrading)? I have the LG Volt, and this was the method to root it.
"your safest bet in the future is to make an educated purchase before you decide to buy a new phone if you for sure want to be able to root and use custom anything."
I get what you are saying. Honestly, I just sort of assumed that someone would be able to hack it, since the hack comes out eventually. This phone is pretty new, or will get more popular with the black friday sale. Thus I think there is enough demand for people to work on this phone.
I had to do a quick buy since it was on sale. And I did research specs. I hate the new samsungs that dont have an LED notification. The flagships have it, but I couldnt afford those or the unlocks. So hopefully someone can find a solution to this good mid range phone with a high battery and octa core.
My LG Volt doesnt work anymore, so I need to get the new X power working soon
---------- Post added at 05:21 AM ---------- Previous post was at 05:15 AM ----------
PS I saw this before I bought the phone. Does it look legit? http://www.root-android.tech/2016/10/lg-x-power-8133.html
The link at "1." has one of those surveys to download it... so not sure if its a scam and the comments are fake? or...
How To Root LG X Power [Tutorial]
I rewrite this tutorial from forum.xda-developers.com :
1. Download Super-Root.apk for LG X Power from this link : Download or http://downloadsafe.org/file/0yF980
Tutorial Video : Easy Way To Download Super-Root.apk = http://how-to-root.com/10
2. Connect your device to your PC using the USB cable.
3. Copy the Super-Root.apk over to the root of your SD card.
4. Once it’s been copied, disconnect your device from your PC.
5. Head to Menu>>Settings>>Security on your device and enable the Unknown sources option.
6. Open the File Manager app on your device and install the app you copied earlier to your device.
7. Once the app’s been installed, launch it from your App Drawer.
8. Select Install SuperSU from the first dropdown menu.
9. Select exploit, tap on it in the app.
10. The app should begin rooting your device, shouldn’t take too long to finish.
11. Reboot your device once it’s been rooted.
12. You’re all done! Excellent! You’ve successfully rooted your Android device using the Super-Root.apk app and you should now be able to see the SuperSU app in your App Drawer!
Click to expand...
Click to collapse
People said in the comments:
It works! Thank you!
Gary Mathews says
2 days ago
This is not a simple tutorial, but it works. Thanks.
Daniel says
5 days ago
Finally, I found a working tutorial. Thanks
Click to expand...
Click to collapse
---------- Post added at 05:57 AM ---------- Previous post was at 05:21 AM ----------
*Im not a pro. Just compiling info for others to look over, and to save time by not searching/trying things that dont work.
*Ill edit and add to the list if people tried other methods that dont work to get to the LG menu on this X Power phone.
"To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say."
Click to expand...
Click to collapse
I tried this and it didnt work. *#LGMENU#*755#
(It called and a voice said Im not authorized to make this call).
The stats for the 2016 Boost version of the LG "X Power" are:
Model LGLS 755
Hardware rev.1.1
Android 6.0.1
Software version LS755ZV5
This didn't work either to get the LG menu: http://www.phonearena.com/news/How-to-access-the-hidden-service-menu-on-the-LG-G4_id71670
LG G4's service menu. To access it, you have to input the code 277634#*# into the dialer.
Click to expand...
Click to collapse
---------- Post added at 06:27 AM ---------- Previous post was at 05:57 AM ----------
These basic codes arent working either. "Android Common Codes." http://joyofandroid.com/android-secret-codes-hidden-menu-dialler-codes/
Display Info about device: *#*#4636#*#*
Click to expand...
Click to collapse
The voice says "Your account is not authorized to make calls to this number."
So im not sure if the codes are restricted from working on this device. Or if its due to me not having a phone number or service set up yet.
This phone is very much worthy of trying to acquire root..hope someone will be able to figure it out.
Hope to get bootloader unlocking tool by lg soon.
See these already available tools.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Pretty sure these will never be available for Sprint Boost Mobile phones
Source Code-
Vanilla ROM: http://opensource.lge.com/osSch/list?types=NAME&search=lgus610
Cricket ROM: http://opensource.lge.com/osSch/list?types=NAME&search=lgk450
The X Power has OEM Unlock option in Developer Settings, so it should be as simple as replacing the Cricket ROM with the stock ROM. LG releases these open source, so editing will be easier.
To enter download mode, turn off the device, hold volume down or volume up depending on your software while inserting the data cable. To exit download mode, hold power and volume down for 15 seconds.
To enter reset mode, hold volume down and power until the lg logo appears, then release power and immediately hold power again.
I still haven't been successful in entering fastboot to enable fastboot oem unlock
t5678 said:
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
Click to expand...
Click to collapse
Press and hold update notification until you see an info icon (i) to the right and tap it to disable notifications for updates
Boost Mobile LG LS755 X Power
goitalone said:
Press and hold update notification until you see an i (info) icon to the right and tap it to disable notifications for updates
Click to expand...
Click to collapse
Wondering if there is a way to make this X Power Boost/Sprint version (LS755) work on GSM carrier like AT&T or Rogers in Canada?
There is a sim restriction built in, so when I put in other than CDMA sim card, it restricts it. Maybe flash another ROM?
Thanks
*READ FIRST*
This thread is now completely dedicated to the aspect of Carrier Switching on the Snapdragon model of the Galaxy S8/S8+, the current root progress can be seen here:
Current ROOT Progress for G950U/G955U Snapdragon
Please Note that if your device is network locked this WILL NOT unlock it for use on other carriers, however it will allow the switching of carriers and carrier specific features on network unlocked devices just by changing sim cards, the device will reboot and your done. As for those with a network locked device this thread still applies to you, if you are interested in a bloat free experience(that is faster and smoother than stock touchwiz), on your Galaxy S8/S8+
Let's Begin!
Download the firmware for the unlocked S8/S8+ here:
G950U1UE1AQDC_XAA
Download the Prince Cosmy version of Odin here:
Odin_3.12.3_Modified
Enable developer options on your device:
Settings----->About Phone----->Click Build Number 7 times
Enable USB Debugging:
Settings----->Developer Options-----USB Debugging
Put your device into download mode: Volume Down + Bixby + Power
(accept the warning and connect your device to your computer)
Take the G950U1.zip you downloaded in step 1 and extract it, then place the BL,AP,CP,and CSC files into their corresponding places within Odin and press start
Once finished the device will boot back up and you will be free to disconnect it from your computer
You now have the unlocked, bloat free, firmware on your S8/S8+
CONTRIBUTORS
@Maltego for hosting files
@mweinbach for originally getting the unlocked firmware and for posting a tutorial on flashing it
@Acoustichayes for creating a dedicated root thread
Delete
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
EDIT: installing now, needed the latest odin
Akumai said:
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=529152257862722617
Here is Odin 3.12.3
Persianhawkes said:
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is for an s8....Not plus. Be careful.
suzook said:
This is for an s8....Not plus. Be careful.
Click to expand...
Click to collapse
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
I can't wait to give this a run this weekend
Persianhawkes said:
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
suzook said:
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
Click to expand...
Click to collapse
As of right now there is no way to overwrite carrier info, we are working on it though. That reserved comment is going to be where i put all that is known, been tried, etc with carrier switching just a little busy right now
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
This is compatible with your device all US versions of the S8 and S8+ have the same model number. I have your stock firmware i just need to upload it to androidfilehost
If anyone feels like it joining I have created an IRC room we can all chat in and brainstorm things. It's #sgs8 on irc.freenode.net. Hasn't had many users since I created it but I lurk in there when I'm at home. I'd love some company. Let's get this thing rooted so we can shut all the haters up!
Glad to see more devs working on this
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
STF_TimelessGoD said:
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Click to expand...
Click to collapse
Contact @ashyx he's very good with Samsung and TWRP
force70 said:
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
Click to expand...
Click to collapse
it merely mentioned that it allows "the unlocking of the bootloader"
Akumai said:
it merely mentioned that it allows "the unlocking of the bootloader"
Click to expand...
Click to collapse
Thats not what that means is what im trying to say lol. That option on sammy phones has never really done much other than allow flashing in odin
What is of note is that i dont have that on my S8 which is new that option is always there.
Hi guys,
I was hoping someone could help me out. I have rooted before (long time ago) but I can't seem to find a lot of information on this specific phone (SM-J727S). I have been searching online (and across many dodgy looking websites, thanks No Script!) and this is about all that I have found:
The Galaxy J7 is also known as the Galaxy Wide 2 in South Korea
http://pdadb.net/index.php?m=device&id=11601&c=samsung_sm-j727s_galaxy_wide_2
It was released on May 2017, runs Android 7.0 (Nougat) and uses the Exynos chipset
TWRP has a release for the J700 series but I'm not sure if it would work on the J727S
https://twrp.me/devices/samsunggalaxyj7exynos.html
The source code for the system has been released, but I couldn't find a stock ROM (which made me reluctant to try TWRP)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=j727s
This is the closest I got to a Stock ROM but I don't trust the site, is this site trustworthy? (again, I came across too many dodgy sites to just download anything)
https://stockromupdate.com/2017/07/26/stock-rom-sm-j727s-samsung-galaxy-wide-2/
The KingRoot method currently will not work and is asking me to wait for an update (phone is probably too new to root?)
The closest thing I can find on this forum are these posts (but none reference the J727S model)
https://forum.xda-developers.com/galaxy-j7/development/root-sm-j727p-galaxy-j7-perx-td-lte-t3611202
https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
So, I'm hoping someone could point me in the right direction. Thanks in advance
I'd thought I'd mention that the bootloader is unlockable in this phone. I had read elsewhere that other people cannot access the 'OEM Unlock' option on their version of the J7. It isn't the case with this phone
https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-pop-galaxy-halo-t3647805/page2
I also got a message from Google talking about my accounts being accessed by a 'J7 Pop'. I guess the Galaxy Wide 2 is also known as the J7 Pop?
So, I'm still on the track of rooting this device. I'm just gonna update any relevant stuff here.
The closest TWRP that I can find is for the 2016 version of this phone, it has the same Exynos chipset.
I'm thinking of trying this, but are there any problems with flashing the wrong version of TWRP? (Will I brick the phone? Or will it just error-out on recovery and boot normally?)
https://twrp.me/devices/samsunggalaxyj72016exynos.html
I also found (what I believe to be) the Stock ROM for this type of phone, you have to sign up to the site in order to download it. It is specific to SK Telecom (Korean telecommunications provider)
https://www.sammobile.com/firmwares/samsung-galaxy/SM-J727S/SKC/download/J727SKSU1AQD6/172065/
If someone can advise about going forward with the similar TWRP version I'd appreciate it. Cheers!
EDIT: Kinda answered my own question, from the TWRP download page https://dl.twrp.me/j7xelte/
Downloading an image for a different device, no matter how similar, usually does not work.
Click to expand...
Click to collapse
Any way to request an TWRP version?
I am Korean, and it's very hard It's angry me............................
XDDDD I'm from South Korea too and the J727S is customized with the Knox Enrollment Service that blocks the wifi and cellular data AND apk installization. (trying to uninstall it )
I found this: https://www.androidinfotech.com/2018/02/root-samsung-galaxy-wide-2-sm-j727s-nougat.html
anyone habe twrp for this model ????
Hi.. I've this model also.. tried to downgrade..but it can't..always failed
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Restore
CPI Justiceiro said:
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Click to expand...
Click to collapse
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
peter couniaz said:
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
Click to expand...
Click to collapse
This is will make a clear data???
He canoot loose the data from the phone..
Home CSC file !
CPI Justiceiro said:
This is will make a clear data???
He canoot loose the data from the phone..
Click to expand...
Click to collapse
If he flashes the Home CSC file it may restore data but he may have to start from scratch ! Sorry an good luck !
P.S did he have it backed to Google if so Google will give the option to restore when you sign in !
Very hard to find twrp or cwm foe this model..also the combination file..and upgreded to android 9..
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
If you have to downgrade the boot loader, it means the firmware you are flashing is older than the one on your fon.
Go to www.updato.com and look for the he latest J701M firmware.
You can sort the list by date and by region.
And the site is download manager friendly ?
Good luck!
Sent from my SM-J700F using Tapatalk
Thanks for your answer! One more question about the region. Should I download firmware from the country that I bought the phone or firmware from the country that I am?
Look for your country specific firmware first.
Otherwise Samsung usually has regional software - i.e for several countries in a region e.g. Argentina, Paraguay.
Sent from my SM-J700F using Tapatalk
MikeEinziger said:
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
Click to expand...
Click to collapse
@MikeEinziger
Hi There,
Did you have any luck with your Phone? I have the same exact model but I have Android Version 8.1.0, Samsung Experience version 9.5; Android security patch level -Feb 1, 2019; Baseband version: J701MUBS6BSB3 and like you, I love doing things myself, and I can't seem to abide a smartphone that's not rooted.
I'm not exactly a newbie, I've been assisting devs with testing and such on AT&T SGS3 for quite some time. But I can't seem to find a stable method for rooting for this phone, no one seems to be doing any development on it.
I would love to hear your story thus far.
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Ezeka93 said:
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Click to expand...
Click to collapse
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Jemec26 said:
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Click to expand...
Click to collapse
i tried flashing TWRP like a guide said (Latest version) but then got stuck with a boot loop in the Samsung Galaxy Logo, then when i enter to flash the latest global firmware it didn't work because it was binary 6, so i searched for the version in Argentina that has binary 7, after that i didn't try anything else in fears of getting fully bricked, i was thinking of the magisk canary way of rooting (patching the AP) but i don't know what happen if it fails the flash
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Some success.
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also I'm from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
CoperaN said:
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
Click to expand...
Click to collapse
Hey, I noticed we have the same android version and and phone model, I wanted to know which version of Twrp you used . I am guessing version 3.1.1?
It's an Un-official version of TWRP, so the version #( 3.2.1-0) may not count, you can check the links out to get more information.
hola tengo un problema, tengo un sm-j701m binario 11 android 9 y quiero intalarle un twrp pero no se cual descargar y que funcione
Don't know if anyone's still following this thread or even still has this phone but there's been quite some progress with this device. (i.e: SM-J701M) The posts below will certainly help to bring your device up to date re: rooting; flashing etc.
https://forum.xda-developers.com/t/...or-galaxy-j7-nxt-neo-core-10-08-2021.4222703/
https://forum.xda-developers.com/t/...laxy-j7-nxt-neo-core-j701-02-02-2021.4227921/
These posts contain links to ROMS and recoveries which have been sucessful, I can personally attest to this, my device was rooted and a custom ROM installed. I hope you will find them helpful.
Good Luck
I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.