hello,
i have a Samsung tab e sm-t561 , it is a NTTF study tab. i wanted to remove their OS and reload to stock rom. but when i try to update it via odin, it gives me error saying that the MDM MODE, CANT DOWNLOAD
REGARDS
I'm not having problems on my.
I own an SM-T561 and I were flashing many times without problems.
I needed to flash stock rom many times because there was no root and tried almost all methods I found, until we found a Russian site doing the root, and their method worked.
Can you verify the kernel and rom version?
unlock your bootloader
recallrules said:
hello,
i have a Samsung tab e sm-t561 , it is a NTTF study tab. i wanted to remove their OS and reload to stock rom. but when i try to update it via odin, it gives me error saying that the MDM MODE, CANT DOWNLOAD
REGARDS
Click to expand...
Click to collapse
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
dvrz said:
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
Click to expand...
Click to collapse
can u tell me how do the boot loader unlock??? in download mode?
i also have this problem please told to disable secure download in odin
passwaord: MDMPass:8152
dvrz said:
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
Click to expand...
Click to collapse
HEY unlocking bootloader using android sdk,
the mdm agent doesn't allow the connectivity to pc.
i.e in device manager no android device is shown. while other devices get connected easily and android device is shown in device manager.please do something
I just rooted my sm-t561 3g device
Hey I just rooted my Samsung sm-t561 device wanting to upgrade to higher version than Kitkat 4.4.4 but couldn't get any solution.
Related
I can't seem to get root on my Sm-T337A.
I want acheive root and learn to develop and experiment with custom ROMS. I'm very new to this.
I was able to install Odin and install a boot.tar file but the Tablet kept boot cycling into recovery mode. I tried what I thought was sidebooting files using adb, but apparently I don't understand how that works yet. I restored the tablet by forcing it into install mode (held down power, vol down, and home) then used Odin to install the boot(LP).tar file which restored the tablet. This ROM is indeed the AT& T Rom, but it is not the same one that came with the Tablet when I got it new (it has a different look).
Please help.
Here is the information on my tablet.
Android 5.1.1
Baseband Version - T337AUCU2BOH4
Kernal Version [email protected] #1 Thu Aug 13 17:01:34 KST 2015
Build Number LMY47X.T337AUCU2BOH4
Knox 2.4
You're SOL, bootloader is locked
gonzo6962001 said:
You're SOL, bootloader is locked
Click to expand...
Click to collapse
I was able to root mine with KingRoot but after rebooting it said I had to take mine to the nearest At&t store. Yea...that won't be happening. Through Odin I flashed the LP boot tar. Fixed it. But I really want to gain root. There is no way around this? There has to be a way to unlock bootloader. Thanks in advance.:fingers-crossed:
NITASHA212 said:
I was able to root mine with KingRoot but after rebooting it said I had to take mine to the nearest At&t store. Yea...that won't be happening. Through Odin I flashed the LP boot tar. Fixed it. But I really want to gain root. There is no way around this? There has to be a way to unlock bootloader. Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
If you could explain how to get around a locked bootloader you would make a lot of people very happy. Can't be done yet. That is the whole issue
---------- Post added at 03:36 PM ---------- Previous post was at 03:27 PM ----------
Look up t337a temp root in xda. A guy says he figured it out but Noone has tried it. I use mine for work every day so I can't chance it. If you're brave enough to try. If it works put in a reply there and let me know. It says it works on our bootloader
---------- Post added at 03:51 PM ---------- Previous post was at 03:36 PM ----------
Here is the link
http://forum.xda-developers.com/tab-4/general/att-tab-4-8-t337a-temp-root-t3301345
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
part fixed
graminou said:
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
Click to expand...
Click to collapse
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
graminou said:
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
Click to expand...
Click to collapse
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
corkiejp said:
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA[/URL] again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
Click to expand...
Click to collapse
Hi corkyejp and thanks, i was aiming to go back to current supported not the beta N release, I officially unenrolled received the OTA image, installed, got stuck in bootloop, tried sideloading MOB30G which i beleive was the correct wifi not LTE version (I saw that version mentioned in my crashlogs too). the device was in developer mode, I think but am not sure, however the HBOOT screens always showed LOCKED. i tried the fastboot flashing unlock (and OEM unlock options) but neither unlocked me. anyway at least I have a device that boots now, will put up with crashes if they occur. thanks again
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
leicablue said:
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
Click to expand...
Click to collapse
Should be as easy as using the "fastboot oem lock" command
leicablue said:
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
Click to expand...
Click to collapse
Any reason you are doing this? The stock debloated, tweaked ROM in development section should give you all the features you need. You can also flash KZD without relocking bootloader.
LG still has a record that you unlocked your bootloader so it's not like they don't know.
ChazzMatt said:
Any reason you are doing this? The stock debloated, tweaked ROM in development section should give you all the features you need. You can also flash KZD without relocking bootloader.
LG still has a record that you unlocked your bootloader so it's not like they don't know.
Click to expand...
Click to collapse
Probably trying to prepare it for RMA
I’m thinking of selling it..Thanks for info.
leicablue said:
I’m thinking of selling it..Thanks for info.
Click to expand...
Click to collapse
Did you manage to relock the bootloader with the "fastboot oem lock" command (as it happens for other models)?
Thanks.
Yes, these are the commands i used to lock the bootloader again (note you have to setup the device again)
Code:
adb reboot bootloader
fastboot oem lock
fastboot reboot
what about the rom?
so when i do lock the bootloader, does the software get checked or updated or do I have to install it manually... what happens after i run all the commands in adb? Im currently on LineageOS 15.1 (LG-h930)
Question I ran fastboot oem lock and now I'm bricked with "your device has failed a routine safety check and will not boot" Does anyone have the fix for this?
MARKREIF said:
Question I ran fastboot oem lock and now I'm bricked with "your device has failed a routine safety check and will not boot" Does anyone have the fix for this?
Click to expand...
Click to collapse
You need to be on a stock KDZ(literally 0 changes) before locking. try booting to download mode by turning phone off and holding Vol+ and plugging into a computer. Then flash a stock KDZ.
thanks but slight problem is the device won't turn off.....
---------- Post added at 02:52 PM ---------- Previous post was at 02:48 PM ----------
ok I'm in firmware update and being seen via LGUP - can you point me in the direction of the latest stock KDZ?>
---------- Post added at 03:04 PM ---------- Previous post was at 02:52 PM ----------
LG UP keeps asking for an update DLL -any thoughts?
MARKREIF said:
thanks but slight problem is the device won't turn off.....
---------- Post added at 02:52 PM ---------- Previous post was at 02:48 PM ----------
ok I'm in firmware update and being seen via LGUP - can you point me in the direction of the latest stock KDZ?>
---------- Post added at 03:04 PM ---------- Previous post was at 02:52 PM ----------
LG UP keeps asking for an update DLL -any thoughts?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
20e is the latest KDZ for US998(i assume thats what you have considering thats what is in your Signature). Use the LGUP_common_DLL_V30_ALL_VARIANTS attachment(there is directions in that thread on how to use that DLL).
tried everything still having dll issues grrrr
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
uninstalled all LG drivers etc rebooted windows 10 reinstalled "LGUP_Install_Ver_1_14_3 .msi" and LGUP_common_DLL_V30_ALLVARIANTS and I'm still getting "error 0x81000302, Please use latest DLL LAF Protocol version is not match DLL= 174187400 Device = 177360928" when i try to flash......
---------- Post added at 04:28 PM ---------- Previous post was at 04:06 PM ----------
Store version 1.14 - DLL Version 1.0.28.9
MARKREIF said:
tried everything still having dll issues grrrr
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
uninstalled all LG drivers etc rebooted windows 10 reinstalled "LGUP_Install_Ver_1_14_3 .msi" and LGUP_common_DLL_V30_ALLVARIANTS and I'm still getting "error 0x81000302, Please use latest DLL LAF Protocol version is not match DLL= 174187400 Device = 177360928" when i try to flash......
---------- Post added at 04:28 PM ---------- Previous post was at 04:06 PM ----------
Store version 1.14 - DLL Version 1.0.28.9
Click to expand...
Click to collapse
Never seen that error. Maybe @ChazzMatt or @runningnak3d would know that one.
also at the bottom of the device screen instead of seeing device info I'm seeing 633A B100 on the top line and Modified / E /L / RO on the bottom
Happened to me as well. Do NOT use uppercut method, as it is not working on Oreo. Instead use lgup dev method. It is working.
As @kanehun stated, you must use the patched LG UP, and you must use partition DL mode (select all partitions) -- upgrade or refurbish won't work.
If you don't want to wipe your phone and just want to get it to boot again, only select recovery, boot and system and make sure that you are using the KDZ for the version that is on your phone. You should be able to salvage your data if you need to.
-- Brian
Does relocking the bootloader basically unroot the v30?
If not, is there a way of unrooting a US998?
charliebigpot said:
Does relocking the bootloader basically unroot the v30?
If not, is there a way of unrooting a US998?
Click to expand...
Click to collapse
If you JUST relock the bootloader you are going to cause LOTS of problems, UNLESS you first restore full stock firmware. Possibly even bricking your phone.
1) You want to flash stock KDZ via LGUP, which replaces TWRP custom recovery with stock Recovery.
Use "Refurbish" or "DL Partition". Then you no longer have root.
2) You can also relock the bootloader AFTER that -- if you wish to get rid of unlocked bootloader warning.
But step #1 will "unroot" your phone.
charliebigpot said:
Does relocking the bootloader basically unroot the v30?
Click to expand...
Click to collapse
Completely different operations.
Unlocking the bootloader allows custom software to run because partition signature checking is skipped. This is what allows flashing and running non-LG ROMs, custom recovery, etc.
Manufacturers don't want you doing this because it enables updating the device once it hits planned obsolescence; they want you to give them another $800+ at that point, not keep updating what you have.
An example I like to point out: the Motorola Droid 4 stopped being supported at android 4.3 (Jellybean). Thanks to Safestrap - the bootloader is permanently fused shut but an exploit allowed loading an entirely different kernel and ROM via kexec after the stock kernel startup- and some particularly determined developers, it's running up to 7.1 (Nougat). The kernel is ancient at this point and spackled together with pieces from Amazon devices, and the phone is a bit slow using a modern O/S because it only had 1gb of memory, but it still works and people still use it as a daily driver because they like it. Last CDMA landscape QWERTY phone and all.
Root privileges are part of Android itself; think of it a combination of Administrator and TrustedInstaller account privileges from a Windows PC.
Google doesn't want you rooting because of the myriad ways the average user can ruin their Android installation by screwing with system files, the many security implications (easy example: let the wrong app have root, now the app has access to any data on the phone it wants and can manipulate whatever it likes), and it making it a lot easier to do things like block ads system-wide.
TL;DR bootloader unlocking is more device-side that disables certain "security" checks to allow booting non-OEM software. Rooting is software-side, lets you use the Admin account in Android for any number of useful shenanigans. They are independent of one another, but depending on the method rooting can prevent a locked-bootloader device from booting.
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Info about the device
For some unknown reason, I can't upload photos, here is the device info:
Model number: SM-S327VL
Android version: 6.0.1
baseband version: S327VLUDS4ARF2
kernel version:
3.18.24-11771718
[email protected] #1
Mon Jun 11 11:55:20 KST 2018
Build number
MMB29M.S327VLUDS4ARF2
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
I have the exact same problem. This is as close as I have gotten to installing custom recovery in order to root my phone
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
Click to expand...
Click to collapse
I think the problem could be that the bootloader is locked. I don't think there is a way to unlock it . I should be getting a new phone here soon, (Moto G6 that allows bootloader unlocking), so I will be able to test more freely with the SM-S327VL without worrying about bricking it.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
Click to expand...
Click to collapse
I need it.
I Want to put the newest Android version on my phone and I Need some help I tried 3 times.
My email: [email protected]
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
From what I know enabling oem unlock is only half of the issue. I assume you forgot the adb steps to perform the oem unlock commands.
Hey guys.
I think I'll get the unlimited pass from Funky Huawei but how does that thing even work?
The page just says that it will grant access to their "tools" but what tools do they even mean???
I have rooted on Samsung and OnePlus before so I don't know why I would need those "tools" in the first place every time I want to access the recovery.
They have hisuite with routed DNS and a modified fastboot. :highfive:
Work to devices Huawei.
In my case, I trying to update the firmware, but problem in my PC, and No update..
A friend , change firmware, me no.
---------- Post added at 03:17 AM ---------- Previous post was at 03:11 AM ----------
https://funkyhuawei.club/instructions
Read this.