Database Users

Read through noob guides but still having problems with the auto BL unlock

I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.

But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode

Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)

You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.

My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think

So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...

Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)

Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)

I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse

live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.

"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem

Thanks everyone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz

If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium

Don't use 7.3

http://forum.xda-developers.com/showthread.php?t=2228534
This says that pretty much doing anything on your kindle fire hd 7.3 or 8.3 and the latest version for kf2 barring rooting and installing launchers will result in a permanently bricked kindle fire hd 8.9(learned hard way) because the 8.9 don't respond to factory cables . You can restore a kfhd 7 and kf2 with a factory cable. I made a thread about that earlier.
If you have a kf don't use the latest version, use the one with the unmatched boot loader
Sent from my jail broken iPhone 5

I believe psych0phobia is developing Kinology 2.0 based on the 7.3.0. I have full confidence in his ability to provide us a working mod rom.
This is a Kinology HD using XDA Premium

Patiently waiting kinology 2.0

got it

miztah1999z said:
http://forum.xda-developers.com/showthread.php?t=2228534
This says that pretty much doing anything on your kindle fire hd 7.3 or 8.3 and the latest version for kf2 barring rooting and installing launchers will result in a permanently bricked kindle fire hd 8.9(learned hard way) because the 8.9 don't respond to factory cables . You can restore a kfhd 7 and kf2 with a factory cable. I made a thread about that earlier.
If you have a kf don't use the latest version, use the one with the unmatched boot loader
Sent from my jail broken iPhone 5
Click to expand...
Click to collapse
i prefer 7.2.1 than 7.2.3 or 7.3.0, why ? it has less bloatware and bugs, they add more things and they fix bugs

I realised the other day that my KF HD 7" has updated itself to 7.3.0 and I've lost my root! I had a quick look on the web and it sent me to a thread on here where the same had happened to someone else, all they did was follow the instructions for the root again and its back to rooted again, I'm sort of half way through doing it now but after reading this I'm gunna stop!
Or do i continue and the problem mentioned by the OP is nothing to do with mine, help?

H17YD_L said:
I realised the other day that my KF HD 7" has updated itself to 7.3.0 and I've lost my root! I had a quick look on the web and it sent me to a thread on here where the same had happened to someone else, all they did was follow the instructions for the root again and its back to rooted again, I'm sort of half way through doing it now but after reading this I'm gunna stop!
Or do i continue and the problem mentioned by the OP is nothing to do with mine, help?
Click to expand...
Click to collapse
What the OP is talking about is doing anything more to it (i.e. installing 2nd bootloader) is very risky since factory cables don't work on the 8.9.
More simpler stuff such as rooting or installing the play store is easier with less (if none at all) chance of bricking.

Protomartyr said:
What the OP is talking about is doing anything more to it (i.e. installing 2nd bootloader) is very risky since factory cables don't work on the 8.9.
More simpler stuff such as rooting or installing the play store is easier with less (if none at all) chance of bricking.
Click to expand...
Click to collapse
Ahh right!.
Thanks you for clearing that up for me, I'll try and re-root it!

I hope someone can help me.
After my KF HD 7" running 7.2.3 updated itself to 7.3.0 i lost my root but I have now rooted it using v27 binary and qemu root as the guide on here shows. Everything worked perfect and i can use blackmart alpha again. But when I click on SuperSU I get the message The SU binary needs to be updated. Continue? I press continue and get the option to use normal or custom recovery so I press normal. Then after a minute or so i get the error installation failed!
I have searched for a solution but nothing is the same as my issue on this device.
I have SuperSU installed and superuser (when I try and open this I get superuser has stopped)
I have tried uninstalling SuperSU and re-installing it but still the same!
I can still install apps by downloading them on blackmart alpha then using ES explorer to install them. Where before blackmart used to do it itself.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root Bin4ry Ver 28 http://forum.xda-developers.com/showthread.php?t=1886460

miztah1999z said:
http://forum.xda-developers.com/showthread.php?t=2228534
This says that pretty much doing anything on your kindle fire hd 7.3 or 8.3 and the latest version for kf2 barring rooting and installing launchers will result in a permanently bricked kindle fire hd 8.9(learned hard way) because the 8.9 don't respond to factory cables . You can restore a kfhd 7 and kf2 with a factory cable. I made a thread about that earlier.
If you have a kf don't use the latest version, use the one with the unmatched boot loader
Sent from my jail broken iPhone 5
Click to expand...
Click to collapse
Just so you know, Factory cables are not required to put the 8.9 into fastboot, There's another way to do it.
Disconnect your device from the PC and turn it off, And From anywhere on your pc where you have access to adb.exe and fastboot.exe (Like C:\KFFirstAide) , Right click and choose Open command window here
Type this command
Code:
fastboot -i 0x1949 getvar product
You'll get "Waiting for device"
Connect your 8.9 using the normal cable, It will power up and get into fastboot mode
So your KFHD 8.9 might not be permanently bricked after all.

For me 7.3.0 has done everything better, it may be that the battery is running to fast empty but I think this is fixed in 7.3.1... However, i'm using kinology 2.0.1 and everything works fine!
Sent from my KFTT using xda app-developers app

why? why not?

I updated to 7.3/8.3 to much dismay. Contrary to what OP is describing, I have since installed the 2nd boot loader and am now happily running CM10.1. So further modification is still possible.

Update rooted VZW S5 from Lollipop to Marshmallow?

I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0?
If I need to wipe the phone, that's OK.

RBEmerson said:
I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0? If I need to wipe the phone, that's OK.
Click to expand...
Click to collapse
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
[/...]
Click to expand...
Click to collapse
Thanks!

RBEmerson said:
Thanks!
Click to expand...
Click to collapse
Not a problem at all!
Just keep in mind that, even though the following area of the forum is specific to the Verizon GS5 (kltevzw)...
https://forum.xda-developers.com/verizon-galaxy-s5
... the following area of the forum is specific to the Galaxy S5 (klte...) variants because of the "Unified Developments" that also include the Verizon GS5 (kltevzw) device.
https://forum.xda-developers.com/galaxy-s5
Also (in case you may have wondered about it) the Verizon GS5 (kltevzw) device has the "Snapdragon" processor. Be sure NOT to use anything that falls under the "Exynos" category or similar.
I wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Quick question before I follow your suggested links - is there a quick way to determine what processor is in the phone? I distinctly remember the issue of the processors when rooting. AFAIK the only hardware info is G900V.05. When I booted into recovery with TI, no TWRP, etc., just the stock recovery screen.

RBEmerson said:
I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0?
If I need to wipe the phone, that's OK.
Click to expand...
Click to collapse
1. It's impossible to update from 5.0 to 6.0 witout losing root. You will have to gain it again if possible.
2. Root is possible on 6.0 for G900V with Samsung EMMC chips.
3. You can check which chip your phone has with EMMC Brickbug Test app from the Market. Just run it and look at the first two figures in CID line on the info screen.
They will be 15 or 11.
15 - Samsung memory, root is possible on 6.0.
11 - Toshiba memory, root is impossible on 6.0.
For both variants root is possible on 5.0.

RBEmerson said:
Quick question before I follow your suggested links - is there a quick way to determine what processor is in the phone? I distinctly remember the issue of the processors when rooting. AFAIK the only hardware info is G900V.05. When I booted into recovery with TI, no TWRP, etc., just the stock recovery screen.
Click to expand...
Click to collapse
I had stated on the last statement that the G900V has a Snapdragon Processor.
I can't state that what your looking to do is possible since I've never performed this but, the threads i had provided are where you can, at least, get some additional member guidance.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
I had stated on the last statement that the G900V has a Snapdragon Processor.
I can't state that what your looking to do is possible since I've never performed this but, the threads i had provided are where you can, at least, get some additional member guidance.
Good Luck!
[/...]
Click to expand...
Click to collapse
I think bbsc pretty much nailed down the go-nogo for me. Thanks again, guys. Good on ya!

CID begins 15... woohoo!

RBEmerson said:
CID begins 15... woohoo!
Click to expand...
Click to collapse
Glad to see it makes you happy.
Now you have to look around and decide what ROM you want.
Should it be a stock ROM or something other?
There're several good guides on flashing and rooting in Verizon Galaxy S 5 General section.

A) where is a good place to continue this discussion? I don't want to be OT B) I've managed to screw myself into the ground and somehow lost the basic ability to load anything via Odin. The problem's in the phone. I somehow landed in what seems to be an engineering version of 4.4.2. Which would be annoying but OK IF... Power/Home/Vol Down brought me to push Vol Up letting Odin do the rest. Instead, all I get is "Power Reset or Unknown Upload Mode". The only way out is the same three buttons (Pwr is ignored). Booting up, I get a generic Samsung background, across the bottom, four Andy's with 15 on one, possibly numeric keypad on the next, app drawer, HW on the next Andy, and FAIL on the last (oh how so true!).
Apps on the screen include CPUStress, Waterproof, SEMI, Factory IME, RX_AGC_LE and MIC2 Echo.
Where am I? How do I get back normal uploading? Odin has utterly no idea about how to do anything useful with the phone, although it acknowledges it's there. Ditto for file explorer on Win10.

Oh yeah, and I have a black window filled with yellow info describing the phone, memory, cameras, etc. The first two lines might help (or not):
PDA: FA44_G900VVRU2APA1
Phone: G900VVRU2AOI1
The window doesn't appear to close, move, or go away. Attempts to open the app drawer are covered by a not totally opaque black foreground.
"Toto, I don't think we're in Kansas anymore."

The ugly wreckage:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RBEmerson said:
Where am I? How do I get back normal uploading?
Click to expand...
Click to collapse
The ugly wreckage:
Click to expand...
Click to collapse
What do you want to achieve?
Just practice in flashing or something else?

bbsc said:
What do you want to achieve?
Just practice in flashing or something else?
Click to expand...
Click to collapse
I want to be back to a sane loader and 6.0.1. The instructions I followed clearly were brainless in recommending, after, G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5, using COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5. If I can flash the first file, I'll be back to 6.0.1 and then I can spend a lot more time planning rooting that.
As a side question, I assume that VZW's seriously locked code is still present on my S5, right?

RBEmerson said:
I want to be back to a sane loader and 6.0.1. The instructions I followed clearly were brainless in recommending, after, G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5, using COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5. If I can flash the first file, I'll be back to 6.0.1 and then I can spend a lot more time planning rooting that.
As a side question, I assume that VZW's seriously locked code is still present on my S5, right?
Click to expand...
Click to collapse
Yes, "VZW's seriously locked code" is there forever.
But we're trained to live with it at present time.
Try to take the battery off for 10-20 sec, insert it back and boot to Odin mode.
But don't flash anything more, just tell me if there is any success.

No change. BTW, there's some text in the UL corner:
Wait...
Done
UDC Start
And then a standing Andy with a little speech balloon and then "POWER RESET or UNKNOWN UPLOAD MODE" as before. IIRC there may have been an error code in the UL but that's not there. Maybe the battery pull changed that, maybe not. Meanwhile, I'm going to try some other button "gestures" to see if the produce something else. Probably not... "Insanity is doing the same thing over and over again and expecting different results." - - ≠ Einstein

The situation is definitely abnormal. This shouldn't happen.
A USB jig can help to get to Odin mode but I don't think you have one.
I'd try these variants:
1. Boot the phone into this abnormal boot mode, run Odin and connect the phone to the PC. Then press and hold Power, Vol- and Home till the phone reboots (more than 10 sec) and see if it reboots to Odin mode.
The second variant will be later.

No change. BTW, there's some text in the UL corner:
Wait...
Done
UDC Start
And then a standing Andy with a little speech balloon and then "POWER RESET or UNKNOWN UPLOAD MODE" as before. IIRC there may have been an error code in the UL but that's not there. Maybe the battery pull changed that, maybe not. Meanwhile, I'm going to try some other button "gestures" to see if the produce something else. Probably not... "Insanity is doing the same thing over and over again and expecting different results." - - ≠ Einstein
And this is about the only result:
Vol Up + Pwr

Ok, here's the second variant:
- Boot to system.
- Press "Andy" with black dialpad and dial *#9900#
- You should see a menu. Press "Debub Level ..." button and select High.
- Power off the phone and try to boot to Odin mode.

Bought a Samsung Tab A SM-T387V, apparently has doordash on it, how can I wipe it and use it as a normal tablet?

EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!

Which Android version did you flash? Did you finally get rid of MobiControl?

XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!

genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?

I had no luck. I can't flash anything, got error "MDM mode, can't download ".

XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.

genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?

XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3

genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?

XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.

genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?

XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.

Any idea where you downloaded it from? I cant seem to find a link.

quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/

"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50

Question How I can obtain a firmware file for this device?

Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!

Josephdbrewer25 said:
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Click to expand...
Click to collapse
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.

SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device

SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.

Josephdbrewer25 said:
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
Click to expand...
Click to collapse
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Josephdbrewer25 said:
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Click to expand...
Click to collapse
Newer devices doesn't have a dedicated recovery partition.

SubwayChamp said:
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Newer devices doesn't have a dedicated recovery partition.
Click to expand...
Click to collapse
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.

Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
My device is the Cricket Dream 5G EC211001. It's weird

Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
It doesn't really need to stay in preloader, this is the whole purpose of this tool, preloader is, actually, useless for flashing, when you press the two volume buttons, the device enters to preloader mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you installed correctly the drivers, then, mtkclient detects the device, in the short time, and make it return to BROM mode through a handshake, to bypass the DA/SLAA authorization,
BROM mode is disabled by OEMs, similarly to EDL point, without this kind of tool, no more remedy that opening the back cover.
Moto 1st gen, it's a long time ago. It is placed in a tiny portion of the ramdisk, but you don't need to find where’s located.
If you think to port it, actually is not as easy due to newer implementations, A/B slots, virtual slots, a way to fix it permanently, etc., but basically what you need is in the boot image