Hi everyone,
I've got a TB-X704L (a Lenovo Tab 4 10 Plus).
I managed to get it, some time ago (about Jan), to root it and (with a lot of help from people on here) get Magisk running, installing Android 9.
There, sadly the good news ended. As of about March (so around 10 weeks after I got it going), Magisk stopped passing Safetynet attenstation.
It passed basic integrity, failing ctSProfile.
I've hung on, hoping for an update that might fix it, but no, as of September we're still on 23.0 (23000) and still failing, which wipes out the reason for the tablet!
So what I'd like help with is;
- Is there a simple way to fix this Safetynet issue?
- If not, what's the best plan; to go back to stock or install a new rom?
- Any good guides on either from where I am?
I'm no noob, but the investment of time on this so far has been pretty huge!
Help much appreciated.
Thanks all,
Any help?
Any ideas how to get back to stock? or If I would sort my magisk problem by installing a different os?
Related
:crying: -Sigh- Alright, this has been a pretty stressful two days so I'll try to be as specific as I can.
Device details:
- Samsung Galaxy Tab 4 10.1 T530NU 16 GB Black with WiFi capabilities.
- I was running Lollipop 5.0.2.
Problem:
I wanted to get Xposed installer on my tablet, and found out if I wanted to get the modules I wanted working with what I wanted to do, I needed the Xposed Framework installed onto my tablet. I went to research on how that works/what do to to get that up and running for me, and I found out I needed TWRP, had to add it on my tablet with Odin, and then add what I needed for Xposed in a custom boot through my SD card.
As soon as I got TWRP on my tablet, I've been stuck on a bootloop.
Things I've tried:
- Wiping all data.
- Clearing cache/dalvik.
- Charged to full, and retried clearing cache/wiping again.
Additional Details:
- I have access to a PC
- Able to connect my tablet to a PC via USB cord.
- I'm in the US (Since I've some some region specific things floating around)
What kind of help I'm looking for:
- A updated(?) and working stock firmware for my device.
- TWRP version that will work properly on my device.
- Xposed framework ZIP to add to my device.
I've been spending hours and hours trying to find websites and threads on here and on the internet in general to help me fix it, or find stock firmware for my tablet to start over from scratch. I have had no luck anywhere at all. My desktop is just piled with .ZIP files that have claimed to work but no longer work(?).
I'm just at a loss...It's really diving me crazy. So, as a last resort, I'm writing to see if I can get some help on here. I'm not one to really ask for help on things like this..I usually do enough research to figure it out but I feel like I've visited every single thread/site I can and have had no luck. I would greatly appreciate some guidance
Resurrecting this thread after over a year hoping someone is paying attention...
Tying to the thread hopefully getting enough people talking about this... again.
forum.xda-developers.com/tab-4/help/samsung-galaxy-tab-4-10-1-sm-t530nu-t3441044#post74700970
I have the same problem as well. I have downgraded from 5.0.2 to 4.4.2 hoping that would work. I flashed PACMAN custom ROM and GAPPS 6.0 nano last night and was able to get in and through setup, but the wifi will not work nor does it detect any nearby networks.
Looking for answers here... Corrupted partitions maybe? I have stable stock ROM's
Maybe sideload APK's to evaluate/fix the issue from the ui side - if any apps exist?
Hi Folks,
I've been lurking and getting great advice form this forum for many years but have finally come up with something I can't fix myself.
I was running a few custom roms but somehow when trying out a few of them I have managed to do something so that I can't flash any custom roms any more.
TWRP which gives an error 7 message (which seems to suggest that my phone no longer thinks it is a moto x play). At present I can install stock roms using ADB but that seems to be about it. I have tried to roll back using a stock rom from the motorola website (LUX_RETLA_DS_LPD23.118-6.1_cid12_lux_retla_ds) but that didn't fix it.
I also can't seem to root my current stock rom (XT1562_LUX_RETEU_6.0.1_MPD24.107-52) but am sure I was able to before i had this problem.
I can't help but think I probably should be grateful that whatever i did didn't brick my phone but I've been trying every idea I can find that over the last few months and nothing has helped. I get the idea it might be some kind of low level partition issue but that is just a desperate hunch. From time to time I've got what seem to be partition errors when try various roms to fix this but they've usually worked their way out.
Any hints or suggestions on how to rectify this would be most welcome.
N
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
but the last 3 days since...
Phone calls Go right to my voicemail box they dont even ring on my phone....
And my [defualt]texting app constantly shows a little cloud crossed out saying no service
Anywheres I had 4gLTE Is now 3g ONLY and i can only do things on the internet thats it, but its slow as a dog.
Airplane mode on-off doesn't work I dialed that *#*# .. (insertnumbers) #*#* for testing and
switching how my phone recieves signal didn't work,
Factory reset from inside my settings + Hard reset from recovery made 0 difference.
Ill recieve all my texts but cant reply to them by rebooting my phone they all come in at once when my phone turns on but them my message app stops working again
-----------
Called my provider (TOTAL WIRELESS,) They said everything fine on thier end nothing they can do. So I called Huawai, and Verizon... got no where.
So im thinking... Its the update patch, or i need a new sim card.. So where / how Do I get the Nexus 6p's STOCK ROM So I can reinstall and how do i do that?
Should i try that? wait for another patch? or request a new sim.... Because as of right now my phones a brick and i use it for work.
Fluttershy_plays said:
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
my phones a brick and i use it for work.
Click to expand...
Click to collapse
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Could you help me find that? not sure 100% on navigation of this website but ill try.
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
--EDIT--
Fixed by going back to stock and starting over.
Fluttershy_plays said:
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
Click to expand...
Click to collapse
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Exodusche said:
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Click to expand...
Click to collapse
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Fluttershy_plays said:
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Click to expand...
Click to collapse
I'm sure there's a way to root with app but just as easy to flash TWRP and install Magisk. Which has nice easy feature of hiding root and passing safety net. That way you get a certified playstore and still use android pay to name a few. If your interested let me know I can explain the process after flashing Magisk.
So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
jekblub said:
So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
Click to expand...
Click to collapse
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
DeathBell said:
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
Click to expand...
Click to collapse
Thank you! Set it as fingerprint, but didn't immediately pass safetynet. Once I installed the universal fix it seemed to work, but also seems to break magisk! Well at least my device says it's certified now lol
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
I don't think you would have to root for that. You can just flash your original firmware to system which was working normally. You can find the files on the internet. You can use Odin and it'll be fine.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
Rooting or flashing custom rom won't help as I've tried everything with my galaxy a50 but the issue still persists. It's related to hardware of the device. Maybe some loose connections in the motherboard. Unfortunately, we don't have skilled local repair guys in India(assuming you too belong to India) who could look into this.
abhi-km said:
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
Click to expand...
Click to collapse
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
abhishekpandey.468 said:
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
Click to expand...
Click to collapse
If you under clock all cores below 1ghz and set selinuxe to permissive mode then magic happens.not even single reboot in last 26 days. Before it was restarting every 5, 10 minutes.
I am also facing the same issue with my M21, downgraded to android 10, but it didn't help. Any suggestions?