Database Users

Amazon Prime Moto G4 Nougat soak test/Indian release.

After browsing a bit I was excited to see that there has been an official Nougat release of sorts for the G4, being that my phone's bootloader is not unlockable and installing custom firmware is not an option. After reading the instructions released for the Indian version I noticed that it required MJP24.139-63/64 and I have MJP24.139-64/65. Being the adventurous soul that I am I attempted to install it. As expected I get an error that says as much, that it expects MJP24.139-63/64 and has found MJP24.139-64/65. To see if there was a way I could downgrade or if there were another version of Nougat that didn't need this I looked around some more and found this. Those instructions link to a guide that seems more focused on getting you *back* from Nougat than they do on prepping your device for it and as such those instructions link to the official Motorola website that only has the latest available firmware (what I currently have installed). The only other advice I've seen anywhere about what to do all links to a Reddit post that has subsequently been deleted so I have no way of knowing what it said.
Does anyone know what to do? Is this even possible? I would very much appreciate any help you all can offer.

MoseIlla said:
(...)As expected I get an error that says as much, that it expects MJP24.139-63/64 and has found MJP24.139-64/65.(...)
Click to expand...
Click to collapse
What is that error message?

lerg96 said:
What is that error message?
Click to expand...
Click to collapse
It's as I said, it said it expected 63/64 and that I had 64/65

Custom ROM on T-Mobile branded S5

Hello people,
i bought a Galaxy S5 with the model number G900T3 and want to install AOKP on it. (https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aokp-mm-t3293839)
This is the first time i want to flash my smartphone and i couldnt find any idiot-proof answers to this. :/
Now my concerns:
I'am in Germany. According to SamMobile is the G900T3 a model for the USA. Will this cause any problems? Will i have problems with a Sim-Card of another provider then T-Mobile?
Can i use the rom for the "normal" klte model?
Will the Custom ROM remove the T-Mobile branding?
Thanks for your answers.

Read thru that thread https://forum.xda-developers.com/tmobile-galaxy-s5/help/difference-sm-g900t3-sm-g900t-rom-t3329337 to get more info on the T and T3 model.
The post #8 https://forum.xda-developers.com/showpost.php?p=66025221&postcount=8 describes the steps to install a recovery and a ROM afterwards.
You should be fine with a klte version because SM-G900T is in the supported devices list here https://wiki.lineageos.org/klte_info.html
For the recovery you can probably also use the current TWRP 3.1.0 . It worked fine for me on a SM-G900F. You can find it on their Homepage. There are many guides around how to flash it with Odin.
At the moment I would recommend you to use lineageos over AOKP because latest nightlies of AOKP get stuck while booting.
If you want to use AOKP anyway use the zip from 2016-03-08. It is the last known working.
About which carrier you can use with a custom ROM I just don't know.
All at your own risk & good luck.

Thanks for your answer.
I think you meant the 2017-03-08-version, right? I would have gone with the latest Marshmallow-version because i thought it would be the most stable.

You're right 2017, not 2016.
I'm not so sure about how actively the MM version is maintained. The first post of the thread https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aokp-mm-t3293839 states the newest release to be 2016-08-03 but on basketbuild there the most recent MM zip is 2017-03-10.
By the way, the Nugat Release is currently without a active maintainer. That's​ probably also the reason why the newer release don't boot.
Only the fact that there are new nightlies on AOKPs every day is unfortunately no clear indicator that they actually work. That's because AOKP has a automatic build system that runs without human interaction but can't test them on a real device.

[TWRP] Issue while flashing it to SM-T385 Oreo (8.1.0)

I was going to root my Galaxy Tab A 2018 (SM-T385) with magisk so
I used the Thread:
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
to flash twrp recovery but flashing it with Odin is not successful due to an error "Only official released binaries are allowed to be flashed."
and hence no twrp then no magisk and no root.
I even tried a downgrade to Nougat but that did not work due to difference in binaries.
Please help on how shall I proceed.

Laura poisini said:
I was going to root my Galaxy Tab A 2018 (SM-T385).........
Click to expand...
Click to collapse
I don't have this device myself but, did you read the whole OP first regarding the OEM Unlock before flashing TWRP?
I would suggest/recommend that you first carefully read the OP for all applicable guidance/instructions and then, if needed, post your question within that thread since it's there for member support and guidance. Those threads are there for providing said support and guidance such questions.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.

Samsung Note 4 Sprint Android 6.0.1 no return 5.0

Hello....!
I am sorry for my bad English skills
I am using Samsung Note 4 Sprint Android 6.0.1.
It's very bad and doesn't have a fingerprint. I need to go back to an earlier version.
I've used "Odin" and "Z3X SamsungTool, COMBINATION". All failed.
I downloaded Firmware at website sammobile.com.
Please Help me...!

If you were on the n910PVP5DQ15 firmware then the sboot is fused5, binary 4 and can not be downgraded. That is most likely the reason you have a fail in Odin. The following links will provide further information and guidance. If you have questions ask then in this post, good luck
https://forum.xda-developers.com/note-4-sprint/help/n910pvpu5dqi5-firmware-download-t3941451
https://forum.xda-developers.com/note-4-sprint/help/roms-installed-qi15-firmware-t3990677

Mr. JAVI said:
If you were on the n910PVP5DQ15 firmware then the sboot is fused5, binary 4 and can not be downgraded. That is most likely the reason you have a fail in Odin. The following links will provide further information and guidance. If you have questions ask then in this post, good luck
https://forum.xda-developers.com/note-4-sprint/help/n910pvpu5dqi5-firmware-download-t3941451
https://forum.xda-developers.com/note-4-sprint/help/roms-installed-qi15-firmware-t3990677
Click to expand...
Click to collapse
Thank you verry much ..!!

Your welcome

Mr. JAVI said:
Your welcome
Click to expand...
Click to collapse
My phone is very cheap...!
I'm not afraid to ruin it
It will help me understand more. :laugh:

Bán Trinh Trả Góp said:
My phone is very cheap...!
I'm not afraid to ruin it
It will help me understand more. :laugh:
Click to expand...
Click to collapse
Well I hope you don't ruin it. lol The Note 4 is concerned by many as "the last develop friendly phone". The Last Spirit update (5DQ15) has made it not so friendly. Prior to loosing my phone, I was on Lollipop
4COK1 with the ultimate Note 5 hybrid (MORA) rom as my daily driver. I could flash back and forth form lollipop to Marshmallow and choose many different custom roms. However, I seldom used MM because I didnt like the layout of the OS. Hated the mock location that force an app and Google maps in Samsung settings (BIG TIME, Yea how moke is it if it connected to Google maps?). While on lollipop just set mock location and done. Furthermore, the permission settings in MM are scattered in different sections that not only adds completely in navigation but confusion as to what the F is this? All the while stating udate for you security. My security or there's? Well, no use crying over spilled milk as they say.
Being locked to 5DQ15 firmware was a new experience. Now years later, I found myself unfamiliar with the Note 4 5DQ15. The first thing I noticed was n910p xda forum was "where did everybody go" ? Next thing I noticed is all the bricked devices and fails in Odin when downgrading the 5DQ15. Thats when I decided the safest choice to begin with was the
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Being with installing TWRP followed by rebooting the phone. Then I rebooted back to TWRP and made a backup of all the partitions to external sd. Afterwards, I flash the custom rom. I was very pleased it had completely with xposed firmware and models. Although its really a great rom, I still missed my old customizations in 5.0 roms.
Reading threw the forums at that time provided very little to go by and the information posted by members seemed to conflict. Some said you you can on 6.0 rom and others saying the opposite. All the while lioking to purchase another n910p with a lower bootloader which lead me to visual prof of custom roms on 6.0 are compatible (maybe). I still needed to flash to be 100% sure. (screen shots in next post).
I also felt like you "Its an inexpensive device and Im going to take a risk".

Mr. JAVI said:
Well I hope you don't ruin it. lol The Note 4 is concerned by many as "the last develop friendly phone". The Last Spirit update (5DQ15) has made it not so friendly. Prior to loosing my phone, I was on Lollipop
4COK1 with the ultimate Note 5 hybrid (MORA) rom as my daily driver. I could flash back and forth form lollipop to Marshmallow and choose many different custom roms. However, I seldom used MM because I didnt like the layout of the OS. Hated the mock location that force an app and Google maps in Samsung settings (BIG TIME, Yea how moke is it if it connected to Google maps?). While on lollipop just set mock location and done. Furthermore, the permission settings in MM are scattered in different sections that not only adds completely in navigation but confusion as to what the F is this? All the while stating udate for you security. My security or there's? Well, no use crying over spilled milk as they say.
Being locked to 5DQ15 firmware was a new experience. Now years later, I found myself unfamiliar with the Note 4 5DQ15. The first thing I noticed was n910p xda forum was "where did everybody go" ? Next thing I noticed is all the bricked devices and fails in Odin when downgrading the 5DQ15. Thats when I decided the safest choice to begin with was the
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Being with installing TWRP followed by rebooting the phone. Then I rebooted back to TWRP and made a backup of all the partitions to external sd. Afterwards, I flash the custom rom. I was very pleased it had completely with xposed firmware and models. Although its really a great rom, I still missed my old customizations in 5.0 roms.
Reading threw the forums at that time provided very little to go by and the information posted by members seemed to conflict. Some said you you can on 6.0 rom and others saying the opposite. All the while lioking to purchase another n910p with a lower bootloader which lead me to visual prof of custom roms on 6.0 are compatible (maybe). I still needed to flash to be 100% sure. (screen shots in next post).
I also felt like you "Its an inexpensive device and Im going to take a risk".
Click to expand...
Click to collapse
I think people can easily buy the latest phones today.
The warranty company assumes all responsibility.
It is difficult to find someone with hobby of editing phone software.

Now just to be perfectly clean, I am in no way suggesting that anyone purchase a pre rooted device. Never
WARNING
To all , You never know what has been installed hidden within the system when purchasing a pre-rooted phone.
If thats not enough, consider the developer of the rom that has put in all the work, cheated out of there donations.

Mr. JAVI said:
Well I hope you don't ruin it. lol The Note 4 is concerned by many as "the last develop friendly phone". The Last Spirit update (5DQ15) has made it not so friendly. Prior to loosing my phone, I was on Lollipop
4COK1 with the ultimate Note 5 hybrid (MORA) rom as my daily driver. I could flash back and forth form lollipop to Marshmallow and choose many different custom roms. However, I seldom used MM because I didnt like the layout of the OS. Hated the mock location that force an app and Google maps in Samsung settings (BIG TIME, Yea how moke is it if it connected to Google maps?). While on lollipop just set mock location and done. Furthermore, the permission settings in MM are scattered in different sections that not only adds completely in navigation but confusion as to what the F is this? All the while stating udate for you security. My security or there's? Well, no use crying over spilled milk as they say.
Being locked to 5DQ15 firmware was a new experience. Now years later, I found myself unfamiliar with the Note 4 5DQ15. The first thing I noticed was n910p xda forum was "where did everybody go" ? Next thing I noticed is all the bricked devices and fails in Odin when downgrading the 5DQ15. Thats when I decided the safest choice to begin with was the
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Being with installing TWRP followed by rebooting the phone. Then I rebooted back to TWRP and made a backup of all the partitions to external sd. Afterwards, I flash the custom rom. I was very pleased it had completely with xposed firmware and models. Although its really a great rom, I still missed my old customizations in 5.0 roms.
Reading threw the forums at that time provided very little to go by and the information posted by members seemed to conflict. Some said you you can on 6.0 rom and others saying the opposite. All the while lioking to purchase another n910p with a lower bootloader which lead me to visual prof of custom roms on 6.0 are compatible (maybe). I still needed to flash to be 100% sure. (screen shots in next post).
I also felt like you "Its an inexpensive device and Im going to take a risk".
Click to expand...
Click to collapse
Sorry for the language differences,
I can not understand everything you write :crying::crying:

Bán Trinh Trả Góp said:
I think people can easily buy the latest phones today.
The warranty company assumes all responsibility.
It is difficult to find someone with hobby of editing phone software.
Click to expand...
Click to collapse
The warranty company assumes responsible with new devices, of course rooting will void the warranty.
Not that difficult to find someone with the skills to edit Android devices. I'll simply say XDA
You are using Z3E tool and Odin are you not? Well then why not buy a newer phone?
---------- Post added at 01:04 PM ---------- Previous post was at 12:59 PM ----------
Its just a hobby of mine, I enjoy moding and flashing. Im not a programer. I simply wish to give back to the XDA community.
I could buy a new phone but the newer models of have locked bootloaders. (us versions).
---------- Post added at 01:23 PM ---------- Previous post was at 01:04 PM ----------
Bán Trinh Trả Góp said:
Sorry for the language differences,
I can not understand everything you write :crying::crying:
Click to expand...
Click to collapse
It not your fault, I know my writing skills need important. Im spelling is horrible.
I thank you as in your first question in this post has help me too. First time I heard of Z3E tool. Thank you

Can't find twrp file that works for SM-350. Please help.

My apologies if I accidently broke the rules with this post. I haven't posted for a long time and I'm a bit rusty on use of this forum.
I have a Galaxy Tab A that I have been trying to load TWRP on, without success. I am convinced the reason is that the TWRP files ae for the wrong hardware.
After calling Samsung tech support here is the info I can provide to identify the tablet.
Samsung SM-T350NZWAXAR gt58wifi-gt58wifixx-smt350 Build number NMF26XT350XXU1CQJ5
Now when I search for the TWRP tar file, the only thing close to a match for the hardware is codename a8hplte . I selected the most recent TWRP file.
Well, I've flashed that tar file using Odin several times but I still get the stock recovery when I boot into recovery .
Is it possible that Samsung has a device for which TWRP doesn't work? I'm hoping someone out there has the same model and can tell me what I'm doing wrong.
Thanks in advance.

Forgot to mention, I sent an email query to TWRP. They didn't respond. No help whatsoever.

No idea where you were looking, but the 1st page of the rom, kernel + recovery subforum for the Samsung tab already has a thread with TWRP for the SM-T350.
Now it's not my specific tablet so idk if it works, but you can just read the thread and ask there.

Nimueh said:
No idea where you were looking, but the 1st page of the rom, kernel + recovery subforum for the Samsung tab already has a thread with TWRP for the SM-T350.
Now it's not my specific tablet so idk if it works, but you can just read the thread and ask there.
Click to expand...
Click to collapse
Thank you very much for taking the time to reply. I had been trying to get a image/tar file from the official TWRP website. Now, I also saw the page you provided a link to. When I read it, I saw that the version (
twrp_3.1.0-1_sm-t350_18317.tar) that was recommended is in a category labeled "for Marshmallow only). What I have is Nougat, and in that category there is no SM-350 TWRP file. So if you would please help me one more time; Should I be using the file from the Marshmallow only category, or the Nougat for SM-355 (which doesn't match what I have)? Thank you again for your assistance.​

BigZ1 said:
Thank you very much for taking the time to reply. I had been trying to get a image/tar file from the official TWRP website. Now, I also saw the page you provided a link to. When I read it, I saw that the version (
twrp_3.1.0-1_sm-t350_18317.tar) that was recommended is in a category labeled "for Marshmallow only). What I have is Nougat, and in that category there is no SM-350 TWRP file. So if you would please help me one more time; Should I be using the file from the Marshmallow only category, or the Nougat for SM-355 (which doesn't match what I have)? Thank you again for your assistance.​
Click to expand...
Click to collapse
Like I said - it's not MY device, so I suggest you ask in the linked thread as the users there will HAVE the device and know better

download ROM/firmware (lowest possible version) from https://www.sammobile.com according to your CSC, repair tablet with Odin3, and unlock bootloader first