Database Users

Need Beginner's Guide, so Custom Rom can be installed

***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!

ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow

No need to downgrade to b29.

lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.

gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works

Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?

kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers

kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?

[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.

[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.

nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????

KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.

kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128

[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.

I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk

Samsung Galaxy J3 sm-j320zn

Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!

Nobody?

mathius89 said:
Nobody?
Click to expand...
Click to collapse
Also trying to find a root for mine. The only thing I haven't tried is cf auto root

mathius89 said:
Nobody?
Click to expand...
Click to collapse
I have an j320w8 samsung please help
Build
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
telephony.lteOnCdmaDevice=0
persist.eons.enabled=true
rild.libpath=/system/lib/libsec-ril.so
persist.security.ams.enforcing=3
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Mon Jan 2 15:19:13 KST 2017
ro.bootimage.build.date.utc=1483337953
ro.bootimage.build.fingerprint=samsung/j3xltebmc/j3xltebmc:6.0.1/MMB29K/J320W8VLU2AQA1:user/test-keys
Sent from my Samsung SM-J320W8 using XDA Labs

j320zn
please help how to rootj320zn me try all root tools :

mathius89 said:
Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!
Click to expand...
Click to collapse
You need V2.79 sr3

Samsung Galaxy j320zn
ashyx said:
You need V2.79 sr3
Click to expand...
Click to collapse
Can you explain what your answer means is there a way to root the phone thats successful?

jdkeys said:
Can you explain what your answer means is there a way to root the phone thats successful?
Click to expand...
Click to collapse
Ashyx means you need SuperSU version 2.79 sr3.
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
Wulfie217 said:
Ashyx means you need SuperSU version 2.79 sr3.
Click to expand...
Click to collapse
If I remember rightly that can be found here on XDA somewhere.

Working root?
What did any users here use to root the J3 SM-J320ZN? I can't get it to root and I'm spitting chips.

mathius89 said:
Hello,
I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...
Help! Thank you so much!!
Click to expand...
Click to collapse
mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?
I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.
I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.
Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?

Winston Churchill said:
mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?
I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.
I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.
Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?
Click to expand...
Click to collapse
J320fn has the same specs so there's a good chance it will work for j320zn

ashyx said:
J320fn has the same specs so there's a good chance it will work for j320zn
Click to expand...
Click to collapse
Thanks for the response.
I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.
Sigh. A bit devastated.

Winston Churchill said:
Thanks for the response.
I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.
Sigh. A bit devastated.
Click to expand...
Click to collapse
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.

ashyx said:
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.
Click to expand...
Click to collapse
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.

Winston Churchill said:
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.
Click to expand...
Click to collapse
If I'm reading that correctly it seems like in Odin you have auto reboot turned on. You need to change that under options, the only thing on in Odin should be F.reset time. Then use (iirc) both volume buttons, gone button and power to restart the phone when it's finished.
For some reason having auto reboot off is important.

Winston Churchill said:
Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.
Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.
It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.
Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.
Click to expand...
Click to collapse
As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.

ashyx said:
As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.
Click to expand...
Click to collapse
Thanks guys.
The problem I'm having is - is there a proper way to boot into recovery from download mode once the flash has finished? I've tried button combos and looked about a bit.
The only thing I've got to work is to exit odin, then take the battery out and boot into recovery using vol up, home and power once I put the battery back in.
When I do that, the Samsung splash screen comes up and in the top left corner it's still saying it's in Odin mode (then it gives my model number and some other details - I can redo if you want to know all the listed details). It appears to just stay stuck at this spalsh screen. I waited about 5 minutes (trying two different times) and it just stays on that splash screen and wont boot to phone or recovery.
Sorry, I'm really hopeless Thanks for your patience.
P.S. So once I take battery out again and restart the phone works fine again because it's obviously reverted to stock recovery again like you said it would if I didn't manually boot to recovery. So it's OK, I've not bricked my phone or anything. I'm just wondering if there's a method I need to do to get it to work other than battery out.
---------- Post added at 05:30 PM ---------- Previous post was at 04:40 PM ----------
I just want to say that I got root for the SM-J320ZN using CF-Auto-Root.
Follow this link to download the package CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip:
https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1
The package came bundled with a version of Odin and some other files, so I extracted them all to a directory, ran Odin, and flashed the .md5 through the AP button. It takes a little while and as it says while it is loading, your phone might reboot several times in the process before it finishes so DON'T interfere with it.
YAY.
Any help on the TWRP issue I'm still having would be greatly appreciated still

420blazedman said:
Also trying to find a root for mine. The only thing I haven't tried is cf auto root
Click to expand...
Click to collapse
root j320zn cf auto root done with odin
---------- Post added at 10:35 AM ---------- Previous post was at 10:19 AM ----------
j320zn root done with cfauto root using odin:

I've finally gotten a TWRP version to work for the J320ZN with no issues. I've had a week of tinkering so I thought I'd go back to my phone and try on that again too after previously giving up.
To repeat what I've already written, the suggested TWRP version for J320FN DOES NOT seem to work. When manually booting to recovery after flashing, you get stuck on the default Samsung boot screen, but with Download Mode text still stuck in the corner (to finally answer your question ashyx)
I got TWRP J3lte to work. To download: https://dl.twrp.me/j3lte/
I've had a BILLION problems doing this... because like the OP, I couldn't get root by using SuperSU.zip through TWRP.... it would cause a bootloop. I tried the suggested version of SuperSU posted by ashyx earlier in the thread... plus the latest with no luck.
My "solution" (LOL) was to flash CF-Auto-Root... without realizing it wiped to stock recovery! So here's me all happy thinking I've got TWRP and root...and gotten rid of the bootloop until I set up my phone and went to recovery to make my first full backup... and saw that not only was I getting stock (DUH lolol), but a dm-verity error.
This is something I know nothing about, other than there is a patch for it. So this time, I decided to try the dm-verity patch and REAL SUCCESS! Root, TWRP recovery (that's still there after multiple checks).
So... if you've tried TWRP j3lte and the latest SuperSU.zip and instead of working, you got bootloop you could try the dm-verity patch in your procedure (also to get rid of the bootloops I just flashed CF-Auto-Root again... but then you'll have to start again with TWRP etc).
My successful procedure was:
1) Install TWRP j3lte as linked above (lastest version twrp-3.2.1-0-j3lte.img)
2) Install SuperSU v.2.82 SR5 through TWRP....https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
3) THEN BEFORE REBOOT, install Dm-verity and Forced Encryption Disabler patch (no-verity-opt-encrypt-6.0.zip) from https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/ using the same "Install" button/method in TWRP.
Then you can reboot and THIS TIME it worked... I've rebooted many times, recovery still there, got root.... Link2SD working fine and I've made several backups to test.
A comedy of errors.....but I FINALLY fixed it just through tinkering. Hope this helps.

Though this thread is probably dead, I did have someone PM me a few weeks ago seeing if I'd found a solution (which is why I've been tinkering). So.....
In future I'd appreciate anyone who follows this updating me about what they had to do - did you get it to work with just TWRP j3lte and the newest SuperSU.zip? Or did you need the patch for Dm-verity/encrypt? It will help me learn what's really going on and why I have to do the things I do. I'm still a novice to things beyond simple rooting.
FOR XPOSED: please note if you're on stock ROM for this device, the Official Xposed Framework WILL NOT WORK. You will land in bootloop. Touchwiz is not supported. You need to install an Unofficial version by wanam. Our chipset is arm so make sure you download the correct version for 5.1.1 arm chipset (not arm64 or x86):
https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure you download the uninstaller.zip for 5.1.1 and have it on your external SD card as well just in case you get into bootloop... then you can go to recovery and just uninstall the framework. This appears to be a custom uninstaller, so use that and NOT the official uninstaller zip for Xposed. It's right at the end of the tutorial (DL link). I had no issues however. Wanam's framework installed fine.
ALSO, the latest (at time of writing) Xposed Installer (apk) v.3.2 doesn't like the unofficial framework - it won't detect it properly plus there are some other annoyances, so I rolled back to v.3.1.5. Older versions shouldn't be too hard to find, but there is a link to an older apk version in the tutorial I just linked with the wanam files.
Finally, If anyone has recommendations for Custom ROMS that work on this model in future, also please let me know here. I'm a bit wary of trying after the trouble I've had with Xposed.

Rooting SM-S920L

Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]

TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.

DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)

friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.

c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.

Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:

c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.

Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.

thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in

My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!

downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!

Walmart ONN 100003652 10.1 inch and gen 2 100015685 series root and CFW / Linux OS!

I know I’m a newb here but I wanted to make a thread dedicated to theses devices in which I I have detailed instructions for rooting as well as CFW’s and unbricking!
I appreciate any donations sent via PayPal email for PayPal is on my profile.

Onn 100003562 Root instructions:
****UPDATE*****
With the newly uploaded rom all you have to do is download use sp flash to install .
May still have to run " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " command in fastboot mode.
Step 1: Downloads
Download Magisk manager and update.
Download ADB & FASTBOOT.
Below I'll have a link for windows. for linux run command "sudo apt install adb".
Dwnload boot.img and vbmeta.img.
Download SP Flash Tools and wwrMTK <---Will make this much faster XD.
I have all of these available
here--> https://drive.google.com/drive/folders/1lREGI_nd7kghuR6vCDjhiOZvbWrpJfBo?usp=sharing <--here.
Step 2:
Install magisk manager and update.
You can either download on the tablet or sideload with adb.
For sideload in windows shift + right click in the platform tools directory and click open power shell here.
Make sure you have MagiskManager-v8.0.0[1].apk saved within this directory.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
For linux Right click the directory in which you have MagiskManager-v8.0.0[1].apk stored and click open terminal here.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
Step 3:
Either make a backup with SP Flash tools or use the boot.img i have provided and copy it to your tablet.
Open magisk on the tablet and click the install then click select image to patch. Locate the boot.img and select it by clicking on it. Watch it finish make sure it fully completes the patch and creates the magisk-patched.img file. Also it may or may not be necessary to patch the recovery.img depending on your system. most likely not.
Step 4:
Flashing the .img files.
Now that you have adb and the images necessary to flash your device power it down and back up holding the volume up key. Once It boots it should load into the bootloader screen click the up key until you have fastboot selected and then click the down key.
Now that you are in fast boot mode you are going to navigate to adb fastboot directory and right click and select open powershell here. again make sure you have all necessary .img files stored in the adb fastboot directory. you should have the patched .img and the vbmeta.img stored in the directory for windows.
Run these commands:
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Wait for it to reboot and then you will be rooted with magisk. enjoy.
I'm always grateful for donations paypal email for donations is on my profile.

Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.

PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets

Okiera29 said:
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Click to expand...
Click to collapse
I'm looking to do the same on my 10", do you think they're interchangeable?

Yes onm

Abelbody said:
Yes onm
Click to expand...
Click to collapse
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.

PleaseBeNicetoMe said:
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
Click to expand...
Click to collapse
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today

Okiera29 said:
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Click to expand...
Click to collapse
Yes it worked too if anyone has the same question

Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)

hightowerc said:
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
I believe that you need to download SP Flash tools if you haven't already. You can then, using the provided scatter file and the downloaded firmware, just reflash the stock firmware to the tablet. You will of course, have to re-root the tablet after it finishes

PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.

KaosKreationz said:
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
Click to expand...
Click to collapse
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com

PleaseBeNicetoMe said:
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
Click to expand...
Click to collapse
thnx ill check this out very soon. im working on a Wiko Ride rn. frp bypass was a total pain took 2 days of trial and error but i was able to bypass.XD

hightowerc said:
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
What’s your system? Did you get it fixed? I know I screwed up my first go round with the 10.1 Bluetooth and such kept crashing after I removed one of the un used features well supposed to be unused. It was the telephony and the contacts and autodialer that caused my issues. But like I stated before there seems to be some kind of wireless data traffic that’s not supposed to be there hidden software wise and it seems to utilize the cellphone apps that are supposed to be unused. Like the original bloatware remover from one of these threads on the original android 9 versions cannot be used bc there is something utilizing the cellphone data apps.
Anyway if there is anything you need firmware wise let me know I’ll upload whatever I have available.

This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless

I used this method to root the new tablet I just picked up, and now whenever I launch any app it freezes my tablet and forces a fast reboot of the tablet, I believe I am on android 10, but I can't confirm as I can't even open settings

okay, so I tried to completely flash the stock images you provided in the other thread, got everything working again, without root, then flashed the patched images you had and got stuck in a screen that just said onn with nothing else happening
edit: I have adb access to the device when it's plugged in so I'm not sure what is happening

Alright, I found out my issue, I was flashing the wrong patched boot img on an older firmware instead of updating to latest, I have gotten a working magisk root on the 10.1 tablet.

So as promised I have attached the lk.bin with the no orange state modification it does still seem to hang for 5 seconds but the ugly message is no longer visible.
this is for the 100003562 10.1 inch model but should work with the newer 10.1 inch models with the MT8768WA chipset that come with android 10.
Installation Instructions:
1. Download lknoorange.bin attached to post.
2. Open either powershell (Windows) or Terminal (linux) where you have the file saved.
3. Put device in fastboot mode by powering on and holding the volume up button and selecting fastboot with volume down button.
4. Use command:
"fastboot flash lk lknoorange.bin"
5. Use command:
"fastboot reboot"
Now you should no longer see the ugly message on boot.
Always love getting donations thanks again all and I wish you the happiest of holidays.

Trixi Needs a Rabbit said:
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
Click to expand...
Click to collapse
I guess i'm kinda lost here at what you may be stating and or asking? what device are you needing help with? I do not have a samsung so i honestly can not be of much help other then to point you in the right direction.
If you need help with a stock image for the 100003562 i have one here.

Onn 7" Model 100026191 TWRP Development

Alrighty... So I'm in the weeds here after going through three variants of the Samsung JPop (Which have bootloaders locked up like Fort Knox) and decided today to break down and dish out $59 for this bargain device. First thing I did upon getting it home was fastbooting it, and was able to unlock the bootloader with no issue. (So easy, a caveman could do it)
I've read just about every thread in here and though there seems to be TWRP support for quite a few models of the Onn tablets, I didn't see this one in here. Right now I have a throwaway laptop which is installing ubuntu for building TWRP for this device. Now, I have NEVER built TWRP. But I have plenty of free time, ambition, and am willing to learn. I have the basic guide to building TWRP open elsewhere. I will take whatever help I can get on doing this, big or small. Building a basic TWRP image should be easy enough, but the guides don't really go into device specific details (as expected), so this is where I could use some veteran help.
Device Specs:
Model: 100026191
Out-of-the-box Android Version: 11
Display: 7" 1024 x 600 Resolution
Processor: 2.0 GHz Quad-core CPU
RAM: 2GB
Cameras: 2MP front & back
USB: Type-C

Ubuntu just finished, and I am getting the build environment ready as we speak. Will keep this thread updated with progress and hickups that may occur along the way. Wish this noob some luck!!!!

Alrighty, so here's what I've been able to come up with as far as more detailed system information. Sorry for the late post, had trouble getting wifi working on ubuntu but got it going.
I suspected a MediaTek CPU and was eager to do a readback with SP Flash Tool, but as you can tell from the provided screenshots, it's actually a Cortex-A53 CPU. my goal here is to some how pull my stock recovery out of here. I thought about dd'ing it but someone in another thread advised against it. Does Onn have stock firmwares hidden away in the internet somewhere? Or is there another tool I can use to pull recovery?

Good evening guys and gals. New day, new opportunity. So i'm still stuck at pulling off boot and recovery from this tablet. I used
Code:
/adb shell cat /proc/mtd
to no avail. Permission denied just like with dd.
Today, I got the MTK droid tool and hooked the tablet to it and got these results. Still no scatter file, still no progress on pulling these partitions. (I apologize for my dumbness yesterday, this device is in fact MediaTek)

Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.

guess i'll return it to walmart
was hoping to root it easily with twrp
just gonna go grab the 8' if this is how it ended for the 7'
thanks for the help though!

I need a firmware for the 100026191

TWRPN00b said:
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
Click to expand...
Click to collapse
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.

Just note that if you want to extract the original boot image, do NOT flash the Magisk image, it will permanently erase the original boot image. There is another way, I can walk you through it.

PseudoDistant said:
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Click to expand...
Click to collapse
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?

alarmdude9 said:
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
Click to expand...
Click to collapse
My way of pulling the images should work on any Android device that ships Android 8.0+, however if you got it brand new, don't update it.

Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.

PseudoDistant said:
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
Click to expand...
Click to collapse
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?

alarmdude9 said:
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
Click to expand...
Click to collapse
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.

After you're done with that, and you're rooted.
`adb shell`
`su`
`dd if=/dev/block/by-name/recovery of=/storage/emulated/0/recovery.img`
Then connect your tablet to your PC and enable file transfer in USB settings, then just pull recovery.img out of your tablet and you have the recovery image.

PseudoDistant said:
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
Click to expand...
Click to collapse
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!

alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Update to Android 12 before using Magisk, just in case.

alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Could you share the ota? This is the same model I'm using but its bricked rn

MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
I will look for it. Saved it to a USB drive and of course it decided to be stupid and it is repairing now. Slow going but as soon as it gets done I will look to see if it survived and if so I will get it uploaded.

MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
Sorry just noticed that the file that PseudoDistant posted is still good. I used this one....
https://forum.xda-developers.com/attachments/magisk_patched-25200_fvdeh-img.5794395/