How can i boot the shield (2017 16GB) into apx / rcm mode?
i have the same question. My intrest is more in tinkering with the tegra x1 in order to get a different root solution not contingent on nvidias closed source crap. I'm running a 2015 foster model and it is getting increasingly difficult to find tutorials on that system specifically with the newer updates. +i am interested in learning the process to exchange the hdd and mopy and manipulate the widevine keys that don't work on mine after the forced 7.2.3 update that occured with all update sofware removed from my system that also fried my controller with a botched firmware update that is blacklisted and not mentioned on the internet except people asking and all replies deleted. you know general unfettered access to the system without the bootloaders say so .
Related
Hello ALL,
I have a utterly abandon asus tablet known as the TX201LA (AKA the TX201LAF). It is the tablet verson of the Zenfone A450CG/A500CG, also similar to the Asus memopad me302c (the Trio is so much like the memopad that it can be flashed with memopad firmware but loses wifi, camera & doc support). These devices all share the same soc and many of the same exact components and device HALS. Roms could be ported relatively easily between these devices with minor changes for hardware.
The reason I am posted here is: Unlock_Tool_A400_v8.1.apk
My device being completely abandon by asus has no unlock tool. So I am on a noble quest to find an unlock tool made by asus that can run on my bootloader to unlock it. The I have tried other unlock tools from the v7 range and none have worked, however the v8.1 actually installs & runs on my device but comes up with the message "device model is not supported". So the unlocked is working against a list of devices burried to the apk which allows unlocking. I researched the tool and it is built for android 4.4 and I'm on 4.2. That variation should not mean much so its all down to the droidboot model & device list. I am on Droidboot 2.0. As much as I can tell the Droidboot 2.0 can be unlocked as it is what is matched to the A450CG model droidboot.
Can someone help me mod this unlock apk so I can unlock my tablet and install CWM built for the zenfone 4/5? PLEASE
If you can't help mod the apk, and you own a zenfone 4/5 A450CG/A500CG can you tell me which version of droidboot is your phone on now? and what version was on it before? Was it 2.0 around the time you have android 4.1-4.4?
I apprciate any input.
Bumpy boompop shazam.. Hello Atoms not DEAD yEt.. https://www.pcworld.com/article/315...m-chip-in-panasonics-2189-android-tablet.html
Humpa lumpa bumpity bump
Hellllllllpppppppppp meeeeee
bump bum bum
Unlocking via hacking/modifying the APK is highly unlikely, I've already researched this route for use on my V500KL
the APK sends a SSL packet (which SSL is not possible to crack) to the Asus servers (mdm.asus.com or mdm1.asus.com/)
this packet contains information about its phone, such as guid and serial number i believe.
I suspect asus has a device list on their end, even if you tricked the APK into sending the packet it would probably get a failure on their end. And the key token to unlock your device is probably hashed with a private key on their end before being sent back to the APK via another SSL connection.
(fun fact, the token, if its the same on all asus devices, is stored in the abootu partition when received, otherwise its mostly an empty part.)
It would be more likely to do a low-level firmware exploit to backdoor into an unlocked boot-loader that doesn't have full capability to fully verify its higher bootloader
(if an exploit exists for that there is, wip on that, for my device V500KL at least.)
sorry for the bad news
I have tried every piece of software and read every forum on the internet and this thing will not root!!!
Kingroot, kingoroot, magisk, framaroot, superSU,
All give me an error saying they are designed for an older system and then crash.
Is it possible that this tablet cannot be rooted? Or that I need to wait for software to be developed or something?
Easily over 20 hours of reading, reformatting, plugging and unplugging and I have tried everything 5 times now.
HEEEEEELLLLLLLLPPPPPPP!!!!!!
bump.
every time i get al the way to the end of the tutorials the tablet says
SECURE CHECK FAIL VBMETA
SECURITY ERROR THIS PHONE HAS BEEN FLASHED WITH UNAUTHORIZED......
Are you flashing the multidisabler ? https://forum.xda-developers.com/t/...of-stock-recovery-proca-wsm-cass-etc.3919714/
And everything you listed there is old and probably will not work on 2019 version.
Try finding the correct procedure for your model in this forum
Samsung Galaxy Tab A series Guides, News, & Discus
Use this forum to find the best how-to guides for the Samsung Galaxy Tab A series and discover the latest news. General discussion also goes here.
forum.xda-developers.com
How to root the tablet A8 2019 T290
Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device :o I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is...
forum.xda-developers.com
Hi there,
I have a Samsung SM-A515x LDU phone, its legally obtained with the right permissions, I also understand it is a 6.X inch tablet as it has no imei or cellular capabilities, I'm looking to do this for the sole purpose of getting updates and getting recent security updates also.
Phone is "clean" I have removed the retail mode lock so phone is fully usable, not rooted and not installed a customer recovery yet.
I live in the UK and spec apps show the phone has having the exynos chip, I'm making the assumption that its likely to be an SM-A515F model (the version it would of been shipped with was a515fxxu1askj/a515foxaskj) But, before i flash all this info through odin, How do I go about making a full backup of the device incase I need to do a rollback, I read about NAND backups but will this truely save me if it gets soft bricked into a boot loop?
attached are screenshots of my update page and my software info page, hopefully this helps.
Yeah I probably would not waste too much time on this device, and no you cannot flash unlocked firmware onto an X variant. The only thing you can do is try to get the demo mode password, but even than you still wont receive any software updates as these "X" variants run on their own update channel.
please help me
I made a fatal error while rooting my nvidia shield tv pro
1 I unlocked the bootloader and successfully rooted according to this topic
Root Nvidia Shield TV Pro 2019 Version
THIS IS OUTDATED https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/ REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE...
forum.xda-developers.com
2 I changed the software to 1-lineage-OS
3 Then I formatted my device and after rebooting the device remains stuck on BootLoader
I tried to flash it again...it didn't work unfortunately
Then I locked the bootloader
After rebooting, a message appeared that no valid operating system could not be found, the device will not boot, then the device turns off
Please Help
Please close the issue. It's resolved
thank you
nisrja said:
Please close the issue. It's resolved
thank you
Click to expand...
Click to collapse
Hi !
Same issue for me.
Could you explain how you fixed it ?
Thx
hi, I've been happy with stock f/w since my first 2015 unit to current 2019 pro unit but going to root my 2019 pro to get smb r/w access. (as far as I know, official system support is limited to read only and only few apps which has its own smb mounter support write access. to find out this was a bummer because I settled with local smb setup to avoid rooting to get rclone! what a...)
so, after hours spent with google-fu, I learned few things and would like to see if I'm ready.
0. I'm on experience 9.1.1 with 2019 pro(mdarcy)
1. there's a magisk module which support what I want, but not sure if it still works. (probably will, but it was written 3 years ago.)
GitHub - dnfm/shield_samba_rw_mounter: Shield TV SAMBA R/W mounter.
Shield TV SAMBA R/W mounter. Contribute to dnfm/shield_samba_rw_mounter development by creating an account on GitHub.
github.com
2. to run that module, I need root priviledge for apps > magisk installed
3. to accomplish #2,
3.1. first have to unlock bootloader, then
3.2. flash twrp recovery or patched bootloader.
4.1. with root, I'll lose ota and ai upscaling in return.(although unrooting and revert back to stock won't hard too much, its not sure you can get ai upscaling back.)
4.2. widevine or safetynet won't be affected by bl unlocking or rooting.
but most articles I found was more than a year old and mentioning experience 8 with 2017 pro, so its not 100% sure.
I'm still not sure which is better and safer way to go, twrp or patched bootloader.
developer image(pre root, adb only) was considered in the first place but dropped because it seems there's no real benefit over consumer image but only could make conflict with magisk.
do you think I'm ready to go? or any advice?
shiree1 said:
hi, I've been happy with stock f/w since my first 2015 unit to current 2019 pro unit but going to root my 2019 pro to get smb r/w access. (as far as I know, official system support is limited to read only and only few apps which has its own smb mounter support write access. to find out this was a bummer because I settled with local smb setup to avoid rooting to get rclone! what a...)
so, after hours spent with google-fu, I learned few things and would like to see if I'm ready.
0. I'm on experience 9.1.1 with 2019 pro(mdarcy)
1. there's a magisk module which support what I want, but not sure if it still works. (probably will, but it was written 3 years ago.)
GitHub - dnfm/shield_samba_rw_mounter: Shield TV SAMBA R/W mounter.
Shield TV SAMBA R/W mounter. Contribute to dnfm/shield_samba_rw_mounter development by creating an account on GitHub.
github.com
2. to run that module, I need root priviledge for apps > magisk installed
3. to accomplish #2,
3.1. first have to unlock bootloader, then
3.2. flash twrp recovery or patched bootloader.
4.1. with root, I'll lose ota and ai upscaling in return.(although unrooting and revert back to stock won't hard too much, its not sure you can get ai upscaling back.)
4.2. widevine or safetynet won't be affected by bl unlocking or rooting.
but most articles I found was more than a year old and mentioning experience 8 with 2017 pro, so its not 100% sure.
I'm still not sure which is better and safer way to go, twrp or patched bootloader.
developer image(pre root, adb only) was considered in the first place but dropped because it seems there's no real benefit over consumer image but only could make conflict with magisk.
do you think I'm ready to go? or any advice?
Click to expand...
Click to collapse
I've tried for hours! I don't think it's possible to root experience 9. Followed and tried all examples( they are all old using version 8) but failed everytime, even the so called rooted Dev files appear to be normal unrooted os. Good luck, advise if you succeed.