Database Info

[Q] How to get OTA

Hi,
I'm a Gnex user, there is a friend that has a Nexus S, when I saw it she was using GB 2.3.6!
I said, WTF! In know 4.1.2 is official on the Nexus S.
This is the info I was able of gathering:
kernel 2.6.35.7 gb5f63ef
[email protected] #1
GRK39F
How can I update it easily? with stock rom.
Best regards.

Your friend should go to settings and check for new system updates.
Sent from my Nexus S using xda app-developers app

devil188 said:
Your friend should go to settings and check for new system updates.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
yes, she did, but it says "there is no update available"
Thanks.

You could flash the new stock rom for her. But first, try this:
You can try forcing your device to ask for a free download slot:
1. Settings > Apps > All
2. Find Google Service Framework in the list, tap on it
3. First tap Clear Data, then Force Stop
After this procedure the last checked date under Settings > About Phone > System Update should have been reset to 1970 or so. Tap the Check now button there and see if the update notification pops up now.
Click to expand...
Click to collapse
Maybe this'll work, but I can't tell you that it works for 100%.
If it fails, you should definitely download the stock rom OR custom rom (like hellybean 4.2.2 w/ devil kernel) for her and flash it, but you have to unlock & root it for her first.
Hope I can help you out

Same issue!
Hello!
I too have the same problem. I recently got as a gift a I9020A, and before starting to use it as my main mobile I wanted to update it to a newer version of Android. It's current version is 2.3.6 Gingerbread and when I try to check for updates none will appear, I have also tried to clear data and force stop on Google Service Frameworks and then trying to update but once more it was useless. I've contacted Samsung Mobile's Help, they informed me that 2.3.6was the latest Android for I9020A, however I have seen that there are OTAs of the 4.1.2 released for my device.
This is my first android, I wouldn't know the benefits of updating the OS but I assume they are many, I have an iPad and I jailbroke it without updating the iOS and now if I update the iOS I'll lose the jailbreak and consequently all of the cracked apps, but I can't install apps that require a more current version of iOS, so I'm taking that experience to Android, don't ever want that to happen again.
I have already non-destructive rooted my device following this thread, but I don't know any much further than this, or even if the rooting I needed was the destructive one in order to apply the OTA. I saw this thread with the links for the OTA 4.1.1 but am not sure of the differences between IMM76M and IMM76D, so I don't know which to download..
I'll be glad to provide any other information needed. If anyone could help OP and me I'll be very grateful, give you a thank you and set the good word of you on the streets. "Street Rep +1" lol

Download the "sojua" one at this thread: http://forum.xda-developers.com/showthread.php?t=1932832
Then flash it (If you don't know how it works, just take a look at some tutorials!).

So I should install the sojua and not the OTA, right? The OTA would be only from the ics to jb?
And I don't know how to flash, by what I've read I have to use Clockworkmod Recovery? if so I think I can find tutorials easily, if not then please pinpoint me the right way, there is far too much information out there, I feel overwhelmed..

Anyone?

"sojua" from the thread IS the OTA version!
Also, I think you need this too: https://dl.dropbox.com/u/41124284/gapps-jb-20121223-signed.zip (Google Apps, for installing all the G-Apps)
To flash your device with CWM, you have to:
1. Install "ROM Manager" (@ Play Store, search for it)
1.1 Enter USB-Storage mode and copy the .zip file into your sdcard.
2. Open ROM Manager and install Clockwork Recovery (Simple)
3. Turn off your device after the installation has been finished.
4. HOLD Volume Up and the Power Button to enter Recovery Mode.
5. Select "RECOVERY" by using the volume button and press the Power Button to confirm.
6. After CWM has come up, select "backup and restore" first and backup your system. This may take a while.
7. Make a factory reset (at the main menu) // EVERYTHING will be wiped!
8. Go to "advance" and "wipe dalvik cache"
9. Main Menu > "install zip from sdcard" > select the zip you copied into the sdcard. (Select the OTA!)
10. Wait until finish
11. Repeat 9. , but now select the gapps zip.
12. Wait until finish
13. Main Menu > Reboot to system
You're done! If something bad happens, you can always restore by going into recovery mode and select "restore" in the "backup and restore" menu.

Thanks a lot, devil188, but unfortunately it still hasn't worked..
I get up to step 9-10 and then it will abort the update I don't know why. I've tried unzipping the Sojua tgz file, leaving only the tgz file, unzipping the tgz and zipping it into a .zip.. but it will always abort
Not sure how to proceed now

I will look for the file you need for flashing. Be patient actually, you could try to flash a custom rom, maybe you like those ones more
Sent from my Nexus S using xda app-developers app

Any news?

Try searching the stock rom in the forums or flash a custom rom (<better ), it's fast to find
Can't do it for you now because I'm not at home right now
Also, if you decide to flash a custom rom, then follow my little tutorial
Sent from my Nexus S using xda app-developers app

I can't post a link I have to a DroidViews tutorial, since I have less than 10 posts, but by what I understood it would replace the factory image from mine 2.3.6 to a 4.1.2. Is there any problem with that?
Moreover, what Custom Rom would you recommend?

I've managed to finally be able to upgrade my Nexus S to 4.1.2 following the DroidViews tutorial. Now I'm having battery issues lol.
Thank you very much for trying to help me

No updates. Ever.

Hi All
Hope you can help (because Huawei can't..)
I've had a Mate 8 for just under a year now and i've never had an update. Not one. A close friend bought one at the same time (different place) and has recently had the EMUI 5 update. I am still on EMUI 4.0 and have not had a security update since feb 2016. The handset was originally purchased in Germany and besides the update issue has worked flawlessly here in the UK. I would like the update however and do n ot mind if its manual and not OTA but Huawei are unable to offer anything like a solution. Does anyone know how i can update this handset without bricking it which is what concerns me. If it helps it is as follows:
NXT-L29
Build: NXT-L29C900B170
EMUI 4.0
Android 4.0
Thanks in advance

Hi,you have Global Version.I think for C900 there is no Ota Update,i can't see in the Firmware List
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
I converted my C636 to C432 and all Ota Updates is coming

Ah ok, I've had 'global version' mentioned to me before. How can I convert to a different C variant and if I do do you think that will enable ota updates?
Sent from my HUAWEI NXT-L29 using Tapatalk

I think you can update to NXT-L29C432B192 via "dload". If it works, then Nougat update will be available. But for more sure, let's other guys from this forum confirm that.
Good luck.

ronnie72 said:
I think you can update to NXT-L29C432B192 via "dload". If it works, then Nougat update will be available. But for more sure, let's other guys from this forum confirm that.
Good luck.
Click to expand...
Click to collapse
Yes, I also believe that it is so possible

ronnie72 said:
I think you can update to NXT-L29C432B192 via "dload". If it works, then Nougat update will be available. But for more sure, let's other guys from this forum confirm that.
Good luck.
Click to expand...
Click to collapse
OK, thanks for the info.
Since had it confirmed that the hadset is a US variant (San Diego) and as such is trying to connect to US servers not UK which is why it can't the OTA update.
With this in mind will the dload method still work and if so, and sorry to be a total novice, but how to i do the dload method? (massively do not want to brick the phone)
Thanks again all,

1. Download the update on the computer.
2. Unzip.
3. Create a folder "dload" on micro SD card and copy only UPDATE.APP inside.
4. Turn off the phone and put mitsro SD card.
5. Turn ON the phone.
6. Go to "Updater" and click on "Local update".
That is it.
If update is not suitable to your phone "Installation failed" will be displayed at the screen and phone will be turn to the present state.

ronnie72 said:
1. Download the update on the computer.
2. Unzip.
3. Create a folder "dload" on micro SD card and copy only UPDATE.APP inside.
4. Turn off the phone and put mitsro SD card.
5. Turn ON the phone.
6. Go to "Updater" and click on "Local update".
That is it.
If update is not suitable to your phone "Installation failed" will be displayed at the screen and phone will be turn to the present state.
Click to expand...
Click to collapse
Superb stuff, thank you. Only question now is where do I find the update file?
Cheers
Sent from my HUAWEI NXT-L29 using Tapatalk

On this page link for NXT-L29C432B192 (update.zip) - https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727 :good:

ronnie72 said:
On this page link for NXT-L29C432B192 (update.zip) - https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727 :good:
Click to expand...
Click to collapse
Thanks very much. I'll give it a go this evening. Find gets crossed.
Cheers
Sent from my HUAWEI NXT-L29 using Tapatalk

ronnie72 said:
1. Download the update on the computer.
2. Unzip.
3. Create a folder "dload" on micro SD card and copy only UPDATE.APP inside.
4. Turn off the phone and put mitsro SD card.
5. Turn ON the phone.
6. Go to "Updater" and click on "Local update".
That is it.
If update is not suitable to your phone "Installation failed" will be displayed at the screen and phone will be turn to the present state.
Click to expand...
Click to collapse
I have done all of the above but then i go in to settings, update and no local update option is displayed.
Any ideas?

ronnie72 said:
On this page link for NXT-L29C432B192 (update.zip) - https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727 :good:
Click to expand...
Click to collapse
Hi All
I did all above as requested. Could not l;ocate 'uploader' so applied a hard reset and the phone updated although only the security patch.
As it stands build number is the same and no new update available.
Updater appears in the app list but no where to be found on the phone and the update in settings provides no 'local update' option.
Odd?

If upload is make it right in this menu after pres three dots shut be option "Lokal Update".

ronnie72 said:
If upload is make it right in this menu after pres three dots shut be option "Lokal Update".
Click to expand...
Click to collapse
Only get this. Is there a zip to the build number you just posted? Would that work?
Sent from my HUAWEI NXT-L29 using Tapatalk

Sorry, I don't know why that happens. Does the phone detect micro SD card? Format again and create dload folder (without quotes), then proceed step by step.
That's all I can advise you.

ronnie72 said:
Sorry, I don't know why that happens. Does the phone detect micro SD card? Format again and create dload folder (without quotes), then proceed step by step.
That's all I can advise you.
Click to expand...
Click to collapse
. It's in there ok but looks like the phone can't recognise the type of file. Just a ? In the box. Could that be the problem?
Sent from my HUAWEI NXT-L29 using Tapatalk

I have no idea. But date 25.May.2011 looks strange. Download again ZIP and try to extract UPDATE tile with another program.
http://www.carbontesla.com/2016/10/download-huawei-mate-8-b192-marshmallow-update-europe/

I have the version L09C636B191
Could I also convert to another version that would have nougat? Do we need an actual SD card? Or just put it in the root folder of our phone?

Enter *#*#2846579#*#* in the Dialer and a menu will open.
Select Software Upgrade--> SDCard Upgrade and then Ok.

erayrafet said:
Enter *#*#2846579#*#* in the Dialer and a menu will open.
Select Software Upgrade--> SDCard Upgrade and then Ok.
Click to expand...
Click to collapse
Hi All,
I've tried again, this time using the newer link file. The phone processes the update all the way through but after restart the build number remains the same:
NXT-L29C900B192
And as such no EMUI 5.0 update is available. Is there anything else i can try? Is there an update file that relates spcifically to the above build number maybe?
Thanks again for all your help,

Updating UK version of ZTE Axon 7 mini to Android Nougat 7.1.1

I have ZTE axon 7 mini from UK Carphone Warehouse distribution. It is single sim + micro SD variant (P852A11_UK). It comes with Android 6.0.1 (zte.20161125.112507) out of the box with no update yet. Screenshot of RECOVERY to compare (see attachment).
I read that there is a way to update this phone to Android 7.1 using the specific update files, but my phone could not detect that files. I have tried many of different firmwares with no success.
Finally, I managed to update my phone, and here is how:
0. BACKUP YOUR DATA just in case. Fully charge your phone. I am not responsible of any damage or warranty void if something went wrong. Use at your own risk.
1. Download Android 6.0.1 Spanish firmware ZTE B2017G V1.0.0B09, so '_UK' will be gone afther update.
Download link:
http://download.ztedevice.com/support/product/570/201612221103982/sd/20161222111119358.zip
Mirror (thanks @NewbieGamingYT):
https://drive.google.com/drive/folders/1hYFuTYBHB5SnDeE2KCOHQf_62xr7EqOL
2. Unzip 20161222111119358.zip and find 'update.zip' file, than copy it to root directory of >internal storage< of your phone. I know some instructions says to copy it on SD card - in my case phone can't find it in 'updates' system menu, and it doesn't work in recovery 'update from SD' as well - phone just restarts after 2 seconds.
You can try to use your SD card firstly, but when it fails, just use internal storage.
3. Shut down your phone.
4. Go to RECOVERY - press and hold VOLUME UP button, then press POWER ON. Wait till RECOVERY shows up.
5. Find "Apply update from inner card" - you can navigate using VOL +/- find 'update.zip' and accept using POWER single press.
6. Wait till its updated. Few minutes in my case.
7. Choose "Reboot system now" in RECOVERY.
8. Go to 'Update' menu and check for updates. In current version, it should be B2017G V1.0.0B09 without _UK.
9. Update to V1.0.0B12 via OTA ('update' function in settings) - it should be available - about 450 MB.
9.1 If it's not available, you can download it manually, and place 'update.zip' in root folder of your SD card or INTERNAL storage:
http://disk.myzte.ru/SW/Axon7mini_B12(SD card software).zip
Mirror (thanks @NewbieGamingYT):
https://drive.google.com/drive/folders/1hYFuTYBHB5SnDeE2KCOHQf_62xr7EqOL
10. After updating to V1.0.0B12 (still Android 6.0.1), you can update to Android 7.1.1 easly (ZTE B2017GV2.0.0B09). Download update (link below) and repeat step 9.1.
http://disk.myzte.ru/SW/Axon7mini_Android7(SD card software).zip
Mirror (thanks @NewbieGamingYT):
https://drive.google.com/drive/folders/1hYFuTYBHB5SnDeE2KCOHQf_62xr7EqOL
That's all! Be patient, first boot after (every) update could take even 10-15 minutes. After all you can check again 'update' in settings, you should be able to make OTA update to ZTE B2017GV2.1.0B12 (security patch 01.september.2017).

Much appreciated that's great thanks very much :good:

Nice guide - there apparently is a last step and that is to do a factory reset after updating I have seen other users say all features are properly available after this
I still await my Global version from gearbest with that £90 offer !

"That's all! Be patient, first boot after (every) update could take even 10-15 minutes. After all you can check again 'update' in settings, you should be able to make OTA update to ZTE B2017GV2.0.0B12 (security patch 01.september.2017). "
Isn't it ZTE B2017GV1.2.0B12 instead ZTE B2017GV2.0.0B12 ? DId you misswrite it or am I missing something since I am on 7.1.1 september 2017 but ZTE B2017GV1.2.0B12.

dyabzhee said:
"That's all! Be patient, first boot after (every) update could take even 10-15 minutes. After all you can check again 'update' in settings, you should be able to make OTA update to ZTE B2017GV2.0.0B12 (security patch 01.september.2017). "
Isn't it ZTE B2017GV1.2.0B12 instead ZTE B2017GV2.0.0B12 ? DId you misswrite it or am I missing something since I am on 7.1.1 september 2017 but ZTE B2017GV1.2.0B12.
Click to expand...
Click to collapse
Yes, of course, I made a mistake! Thank you for letting me know and I'm sorry for confusion !

Cheers, thanks very much, just what i was looking for. Worked out perfect.:good::good:

That great on nougat now :good:

Nice! Will this work for other countries with the "carrier" variant of this phone? Or maybe people can figure that out thanks to OP. Considering picking this phone up at PC Mobile in Canada. Cheers.

does it works with dual sim version too?

I had some issues at step #2 - the update.zip was being rejected with "E: footer is wrong". It turns out that the first 2 times I downloaded B09 Spanish firmware it was slightly corrupted (but not enough to prevent extraction).
Third download of the file gave a different checksum and worked for me. MD5 sum of working file is:
20161222111119358.zip: 1FE524FC244D41DBF39A933A8FB9D00F.
Also, the MD5s for steps 9.1 and 10 (these worked first time for me, but took 3 hours):
Axon7mini_B12(SD card software).zip: 3B5737EAA4527490BA351D2C9693EC00
Axon7mini_Android7(SD card software).zip: EEFD9487846778290A850A868630480D

Tried this on a Canadian PC Mobile model to test it . After the first update it bricked.

Geld801 said:
Tried this on a Canadian PC Mobile model to test it . After the first update it bricked.
Click to expand...
Click to collapse
Damn. Thank you for trying!

if i do this, can i unlock my phones bootloader and load a rom from usa?

does this work on the gearbest version?

Geld801 said:
Tried this on a Canadian PC Mobile model to test it . After the first update it bricked.
Click to expand...
Click to collapse
It look like the Canadians will be stuck with MM on the AXON. I use it for music and on WIFI so, it's working well anyway for what I do. I use it as a wifi phone sometimes because the voice is clearer than my VOIP setup.

Hi
I followed your instructions and managed to update to 7.1.1. but m on B09 not B12. Does not offer me any OTA updates. Security patches are from June 17. Any idea how i can update to B12??
Thanks

i just got my axon 7 mini from gearbest and I'm struggling to update to 7.1.1
i have downloaded the update zip from .es .de and eu but when i transfer over to sd card and run the update scan, it doesn't show up
i renamed the zip file to update.zip
pls help

shub said:
i just got my axon 7 mini from gearbest and I'm struggling to update to 7.1.1
i have downloaded the update zip from .es .de and eu but when i transfer over to sd card and run the update scan, it doesn't show up
i renamed the zip file to update.zip
pls help
Click to expand...
Click to collapse
You have to unzip file that you have downloaded and there will be proper zip (update.zip) inside.

saymonek said:
You have to unzip file that you have downloaded and there will be proper zip (update.zip) inside.
Click to expand...
Click to collapse
OMG Holly FUK!!
thank you!

What did I miss I on the June security patch

S8 Active (G892) Oreo OTAs

Close thread

I missed this, was there an issue?

twizt3d said:
I missed this, was there an issue?
Click to expand...
Click to collapse
If anyone installs it, there is no way back at all AT&T doesn't release Odin files for the phone at all.
Sent from my SM-G955U using Tapatalk

FatalONEM8 said:
If anyone installs it, there is no way back at all AT&T doesn't release Odin files for the phone at all.
Click to expand...
Click to collapse
Ahh so it's the same thing listed in the 892 thread under the s8 (unbranded) forum. Bl2

Bump (sorry mods) new info!
Sent from my SM-G955U using Tapatalk

Downloading bra3 now. Pics and more to come.
Edit. Flashed fine, more to come.

Screenshots attached

twizt3d said:
Screenshots attached
Click to expand...
Click to collapse
That is great that we finally get Oreo for Active S8

norbarb said:
That is great that we finally get Oreo for Active S8
Click to expand...
Click to collapse
Agreed but I think the Odin files were the bigger find

The ARA1 to BRA3 link hangs for me, all others are ok.
Edit: Sorry for being impatient, I waited for the download and have successfully updated to 8.0!

New update available! BRB2! February patch!
Sent from my SM-G955U using Tapatalk

I am redownloading BRB2 now, but my first go around, the update from sd failed, and sideloading failed.
E3005 "/system/HWRDB/data/hwr_en_us.dat" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
failed to open driver control: No such file or directory
E:ensure_path_unmounted failed to unmount /efs (device or resource busy)
Successfully verify for dmverity hash tree Installation aborted.#1
Edit, i was unable to complete this update tried several attempt all resulting in the above error

twizt3d said:
I am redownloading BRB2 now, but my first go around, the update from sd failed, and sideloading failed.
E3005 "/system/HWRDB/data/hwr_en_us.dat" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
failed to open driver control: No such file or directory
E:ensure_path_unmounted failed to unmount /efs (device or resource busy)
Successfully verify for dmverity hash tree Installation aborted.#1
Edit, i was unable to complete this update tried several attempt all resulting in the above error
Click to expand...
Click to collapse
I was finally able to flash this successfully. The issue I had related to the Odin files when I was returning to ara1. Please see the updated post if you need to restore to ara1. Thanks to norbarb and fatalonem8 for assistance with that.

Okay I am a Newbie at this with a ATT Samsung S8 Active
is there a step bye step guidance for this ?
Thank you
Eric

Ericthepilot said:
Okay I am a Newbie at this with a ATT Samsung S8 Active
is there a step bye step guidance for this ?
Thank you
Eric
Click to expand...
Click to collapse
1. Download the update file. ( https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP )
2. Place file on your SD card.
3. Reboot into recovery (hold bixby+Vol up + power)
4. Wait like 15 sec for recovery to boot, may look like it gives you an error but it boots.
5. Select install update from SD card, and select the file that you copied to the SD card.
6. Let it install, after that enjoy Oreo.

bugity said:
1. Download the update file. ( https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP )
2. Place file on your SD card.
3. Reboot into recovery (hold bixby+Vol up + power)
4. Wait like 15 sec for recovery to boot, may look like it gives you an error but it boots.
5. Select install update from SD card, and select the file that you copied to the SD card.
6. Let it install, after that enjoy Oreo.
Click to expand...
Click to collapse
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?

vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
Yes, yes, and yes.
The last link in the OP will update you from QL1 to ARA1 if you need to. Probably better just to install through Odin tho.
You should be on 2ARA1 to update to BRB3, the latest link tells you what version it updates you from and to.
And installing an update.zip will erase your data usually, but there is a way to get around it by turning your phone off at a certain part during the update.

vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
You should update to ARA1, you won't lose data if you flash HOME_CSC. There's a new bypass method for the wipe that occurs during sideload https://pastebin.com/pNKQrfva

FatalONEM8 said:
Recently, we've been able to find Odin files for the G892A they are ARA1 and very new link is here: https://mega.nz/#!d3xxiZiK!63ekoH4Iif2z6MFZ6TJ-2IRcHSh8reO-xZD80KUVUOU
you will need that for these OTAs
Latest:https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRA3-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2AQL1-to-U2BRA3-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2AQL1-to-S2ARA1-UP
These are the OTAs for Oreo, credit goes to @locajm for the Odin files and the OTA links norbarb.
Click to expand...
Click to collapse
Oops, still not used to XDA app ??

vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
You can use the ql1-bra3 ota, to skip ara1, but make sure you follow the guidelines to avoid the wipe.

How to root SM-J337P? Android 9

I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site

Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful

Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.

ashyx said:
Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.
Click to expand...
Click to collapse
tell me about it man. they even let me be a mod!! they must be hard up!! I had better button my lip, dont want any senior mods to think im attempting a mutiny LOLOLOL
it used to be back in the day that people would just accomplish stuff that the mfg said was impossible just to piss them off. Not because they wanted to do anything nefarious with the new found ability, just to poke a stick in their eyes! Man, i miss the OG Evo 4G days
@Androidhelper77 @poppas210 sorry, didnt mean to threadjack, but the root method is available, it just takes some reading of the threads to get there

Thank u

ashyx said:
Root is fairly simple using Magisk pre patched method.
Click to expand...
Click to collapse
This is probably obvious, but what do you mean by "pre patched method?"
EDIT: Nevermind, I figured out what you mean.

Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.) You do indeed need the patched one.
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone. You want the file that starts with "AP"
7. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
8. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
9. Select the firmware img you just copied to the phone.
10. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
11. When Magisk Manager says "All done!" close it.
12. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
13. Turn off the phone
14. Open Odin on PC
15. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
16. Your phone should appear in Odin on your PC
17. Click the AP button and select the "magisk_patched.tar" file.
18. Click "Start" and then DON'T TOUCH ANYTHING!
19. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
20. Close Odin
21. Initial phone setup. Blah blah...
22. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
23. Install Magisk Manager on your phone again (repeat step 6)
24. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!

SlickStretch said:
Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.)
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone.
6. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
7. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
8. Select the firmware img you just copied to the phone.
9. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
10. When Magisk Manager says "All done!" close it.
11. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
12. Turn off the phone
13. Open Odin on PC
14. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
15. Your phone should appear in Odin on your PC
16. Click the AP button and select the "magisk_patched.tar" file.
17. Click "Start" and then DON'T TOUCH ANYTHING!
18. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
15. Close Odin
19. Initial phone setup. Blah blah...
20. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
21. Install Magisk Manager on your phone again (repeat step 6)
22. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!
Click to expand...
Click to collapse
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.

desmond462 said:
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.
Click to expand...
Click to collapse
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.

SlickStretch said:
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.
Click to expand...
Click to collapse
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.

desmond462 said:
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.
Click to expand...
Click to collapse
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)

SlickStretch said:
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)
Click to expand...
Click to collapse
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
then put in phone storage and open magisk manager to install and then select the boot img which start to flash and about few second it said it failed.

desmond462 said:
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
Click to expand...
Click to collapse
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.

SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.

desmond462 said:
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.
Click to expand...
Click to collapse
You're welcome! I'm glad it worked

SlickStretch said:
You're welcome! I'm glad it worked
Click to expand...
Click to collapse
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.

desmond462 said:
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.
Click to expand...
Click to collapse
It sounds like what you're looking for is a "carrier unlock," but I don't know anything about doing that. Good luck.

Been searching for J337P also...
Androidhelper77 said:
I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site
Click to expand...
Click to collapse
The Best explanation / instructional video I've found so far is: h ttps://youtu.be/BOfv0F12gSI
But, TWRP does not have FW for j3topeltespr. And firmwar.mobi misidentified phone as galaxy j7 2016.
Two and a half days of reading and tubing and have better understanding but not much progress.
h ttps://youtu.be/nOGpFJnLP3A

Think I've found everything
poppas210 said:
Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful
Click to expand...
Click to collapse
Think I've found everything
Instructions:
h ttps://rootmygalaxy.net/how-to-install-twrp-and-root-samsung-galaxy-j3-achieve/
The Release:
h ttps://github.com/TwrpBuilderTests/android_device_samsung_j3topeltespr/releases/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_03-45
Question:
Is this the version that causes the boot loop?