Database Users

[Tutorial] How To Restore Verizon Galaxy Tab Back To Stock

If you are here the odds are you are looking to take your Verzion Galaxy Tab back to the default setup for one reason or another.
Here are the steps you will need to take.
First let's make sure you have all the files and things are set up for this.
Hemdall
Download Heimdall from HERE, this is the program you are going to use to flash the needed files to your Galaxy Tab. I am putting the version I use on my sever just in case.
But here is a link to the developers page so you can download the original if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses. (I use Windows 7 and did not need to install this [I think])
Now you will need to install the drivers the is also needed for Heimdall. unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says). (NOT*mass*storage)
Click start and let heimdall download/install the drivers.
Files You Are Going To Flash To Your Tab
HERE is where you *are going to download the files needed to flash to you tab.* There are four files in total.
DOWNLOAD
cache.rfs
param.lfs
system.rfs
zImage
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder " heimdall" and start " heimdall-frontend.exe"
4: Set up the files you are about to flash to the tab in side of heimdall.* It should look something like this.
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP - -* I AM NOT RESPONSIBLE!!
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED.
zImage goes in both the Kernel AND Recovery slot.
system.rfs goes in Factoryfs
Param.lfs goes in Param.lfs
cache goes in the cache slot.
{
"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"
}
5: After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. (I had to push start a few times.)
After this runs you will more than likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery.*(NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall. it will eventually start. sometimes you just need the right combo of plugging in launching the*program.
After this is should be just like you took it out of the box, other than still having root access.
Hope this helps!
Aslo, I did not do any of the work here other than test it out and retype what is on this site to make it available to those on XDA and if you read my blog.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
All credit should go to mike919 at droidforums.net for putting this together!!
You can view his post here.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
Shameless Plug:
If this helped you out would you do me a favor and go to this site and vote/comment?
And pass it along to your friends as well.
Who Pees In The Shower?

Hope this helps some people out around here!

This should be a sticky... Just Saying

Thanks,
I tried to make sure I typed it as good as I could so people like me (mess things up often) would be able to pull it off and host all files I use so that nothing will change.
But I would like someone to look it over and make sure I did not miss something. We are all human after all.
And if there needs to be any other images people can think of to help more people out I will be more than happy to add them.

I cannot find ANY tuts like this for flashing roms, recovery, ect. You, my newfound friend, are the first. We need more exactly like this.
Sent from my SCH-I800 using XDA App

This is great stuff. I messed up a bunch of junk on my VZ galaxy tab and would like to go back to stock. Question about this guide: I've converted to ext4. Can I still follow the steps in this tutorial to return to stock or is there anything else that I need to do first? Thanks very much!

This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer

Bobby Buggs said:
This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer
Click to expand...
Click to collapse
Took the plunge anyway. Seems to have worked. Great tutorial!

Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide

fonixmunkee said:
Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide
Click to expand...
Click to collapse
Yeah, I think I get it wrong more than I get it right.
Last weekend I did this like 3 times in an hour.
Happy it is helping a few people out.

chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?

fonixmunkee said:
chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?
Click to expand...
Click to collapse
No, I tried a few times and did not have any luck. The only thing I am looking to customize with the Tab is really to have it over clocked a little.
I just got the Evo so after I am done setting that up and getting everything worked out I am going to try again.
But if I remember right when ever I run Koush's boot strapper the tab reboots and goes in to recover mode and starts to flash something. (I think, cant seem to remember 100% right now) . Then I get stuck on the Samsung screen..
At that point I am not able to boot back in to recovery mode to wipe anything, but I can boot in to download mode and restore the Tab.
I think I have to be missing something simple?

Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App

fonixmunkee said:
Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App
Click to expand...
Click to collapse
Maybe I am missing something?
Sent from my SCH-I800 using XDA Premium App

hi after restore to stock my screen in blank??help me

this was perfect
you wrote the directions clearer than water bro. thanks! i was dinking around for the 1st time with the tab and screwed something up. i'm back in business!

Your the best... got it first time Great work
- The Mike G.

Had a scary night last night with the old computer/phone/exclamation point error screen but this tutorial helped me out. Thanks a ton.

THANK YOU!
Thanks man! My Galaxy Tab (us cellular branded) was gone after a flash attempt gone bad (black screen and nothing more), but thanks to this tutorial it's finally back to life!!
I LOVE YOU MAN!

VZW Custom Kernel
So out of curiosity, is the Bootstrapper the only way to get a custom recovery set up for the Verizon tab? I used z4root and got the root access, but since then, I haven't had an opportunity to flash roms or kernels because of the lack of a custom recovery. Anybody think they could help ?

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

[GUIDE] BOOTANIMATION LOOP? Look here.

I just finished helping recovering another tablet from an animation bootloop and I figured it might be a good idea to start a thread and share what we've figured out with the community.
If my tablet was bootlooping and I didn't really want to do a whole lot of crazy steps I'd try installing from update.zip before doing all of this. There's plenty of information about that around. But if you find that for whatever reason the stock recovery is totally borked or whatever this method should help.
First. You have to know that this will wipe your tablet. So hopefully you've got backup. Also we need to hope that you have you SBK. If not there is a little on that later. This should work on any A500 with any bootloader. Also I didn't include much about installing from update.zips or how to recover your U.I.D. from your sd card. Those are covered in detail in other threads and are easy to find.
Also. If you have a functioning recovery you do not need this guide. At all.
Webspirit said:
Hello!
I was about to unroot and get back to stock with my A500 so I flashed a stock ROM via CWM to get a ota-update. Before i had a custom ICS ROM installed and now I installed a HC stock ROM. The problem is that i forgot to go through the wipe menu in CWM before the flash and now when I start up my tablet I first see the ACER logo as usual, then a android text-logo which the tablet is stuck at. I've waited 20 minutes and is still shows the same thing. The logo has an animation which i still can see. I've tried to restart the tablet and get into CWM again without succes.
I have read different threads for several hours but I can't find my problem. What should I do? :crying:
Click to expand...
Click to collapse
JdgM3NT4L said:
Here is a brief overview.
What you are trying to do is get into recovery, wipe properly and flash your stock rom. You are going to...
Get the tablet into APX mode.
Use Blackthund3rs APX tool with bundle number 17 and flash it.
Once it flashes and you restart immediately go into recovery.
Don't let the tablet boot or it will instantly erase the recovery that we just installed.
Ok. First get blackthund3rs tool fired up. There is an attachment at the end for this.
{
"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"
}
Choose Bundle Market. and say yes to this...
Hit the View Bundles Tab.
Choose bundle number 17.
Choose to stage the download for flash.
Once it is finished with this...
It will ask for your SBK.
Choose to use the default BCT.
From here follow the onscreen directions for the manual method to enter APX.
Now this is the key to the whole process.
When the tablet reboots you must be holding the volume down button so that it enters directly into CWM.
If you miss it and you see the bootanimation, it will be too late and you will have to start all over.
So when you get to the PASS screen. and you power it off. Don't forget to be holding that volume button when it restarts automatically.
After that it should be as easy and entering the wipe menus, then flash your rom.
I've done this one at least three different tablets and it works everytime.
Good Luck. Please let me know if I can help with any of this.
Click to expand...
Click to collapse
Webspirit said:
How do I know my SBK code?
Great guide!
Click to expand...
Click to collapse
JdgM3NT4L said:
Webspirit said:
How do I know my SBK code?
Great guide!
Click to expand...
Click to collapse
Ok. In the state that your tablet is in getting the serial number (U.I.D./SBK) will be difficult at best unless we get lucky. It is normally pretty easy to find when the tablet has USB debugging enabled. With a new install of a stock rom there is zero chance that your tablet has that enabled.
Soooo...
Hopefully when you've had your tablet connected to your pc it saved the U.I.D. or serial. Or you have a Nandroid backup or some other CWM log. You can find the serials on the sd card for those easily enough. The serial can then be changed into the sbk easily.
If you don't have any of those and you have had your tablet connected to your pc at one time or another, you can try this...
Go to this webpage http://www.nirsoft.net/utils/usb_devices_view.html and scroll way way down to near the bottom and get the program. It is called USBDeview.
Once it downloads extract the whole zip to your desktop. It should be in a folder and have three files inside.
Open the file USBDeview and then first thing choose the options tab/button and uncheck "Display Devices Without Port/Serial Number".
Then make it sort by Description by clicking the words at the header of the list that says " Description". Finally look for an entry about A500, or Acer Iconia A500. Hopefully you see those. Look in the columns to the right and find the column titled "Serial Number". There may be multiple entries. But you can be sure that the one that you need will have 16 digits.
If that doesn't show any results, do this. Sort by "VendorID" ( 1 ). Then look for "VendorID" 0502 that has "ProductID" 3325 ( 2 ). It should show A500 or Acer Iconia A500 ( 3 ) Look in the serial number column if you match those IDs. It will be your serial number/U.I.D. (Thanks to sc2k for sharing this!)
If you do find the number then you are home free.
What you will do now is convert your serial/U.I.D. to an SBK. You can go here and download the program to your pc. Run it and enter your serial number.
If not then there is quite a bit of work ahead. But don't give up. It can still be fixed. And as an added bonus you'll get to play around in Linux...
That thread is here. srbeen posted a great guide and there isn't much that I can add that would help.
Click to expand...
Click to collapse
Once you've completed his guide you should be ready for just about anything. Maybe even world domination. Good Luck.

Nice job with screenshots.
Remember, there is a difference between "bootloop" and "boot animation loop".
Bootloop, is when the device tries to enter the OS, and boots back to the bootloader and original sequence. Over and over.
Boot animation loop, is where the animation continues to loop, is usually caused by bad data that didn't get wiped. Can also be caused by a bad kernel.
Stuck at the Acer screen, is a different matter.
3 different animals. 3 different solutions.
However, any person who puts together a guide, should deserve looking at. The steps are sound and I am sure they will help some users.
Thanks!
MD

Moscow Desire said:
Nice job with screenshots.
Remember, there is a difference between "bootloop" and "boot animation loop".
Bootloop, is when the device tries to enter the OS, and boots back to the bootloader and original sequence. Over and over.
Boot animation loop, is where the animation continues to loop, is usually caused by bad data that didn't get wiped. Can also be caused by a bad kernel.
Stuck at the Acer screen, is a different matter.
3 different animals. 3 different solutions.
However, any person who puts together a guide, should deserve looking at. The steps are sound and I am sure they will help some users.
Thanks!
MD
Click to expand...
Click to collapse
Thanks. I'll alter the title to reflect bootanimation.

JdgM3NT4L said:
Thanks. I'll alter the title to reflect bootanimation.
Click to expand...
Click to collapse
But a good job, and I am sure, it will help others!
And we welcome all guides that help with these things.
Oh, more to your thing, Boot loop. or boot animation, can also be caused by running an ICS rom, on an HC bootloader. Which is more inline with your guide.
Again, good job Mate.
MD

Moscow Desire said:
But a good job, and I am sure, it will help others!
And we welcome all guides that help with these things.
Oh, more to your thing, Boot loop. or boot animation, can also be caused by running an ICS rom, on an HC bootloader. Which is more inline with your guide.
Again, good job Mate.
MD
Click to expand...
Click to collapse
Appreciate the comments, especially when they help keep things clear.
I've never been good at seeing all of the angles, so I'm glad your proofing it for me.
So no worries. And Thanks!
But I've been thinking about it, and this might be a good place to start when repairing any of the issues mentioned. If nothing else it is a near foolproof way to get into a working recovery, albeit with a custom ICS bootloader. But that's pretty easy to get past as well if stock bootloader/rom is what's desired.
So basically, if a working recovery is the goal, it should help.

[Discontinued]

Download and Install LG United Mobile Driver
Download and Install LG Mobile Support Tool​
Boot your phone into download mode:
Put your G2 into download mode by switching it off, hold the Volume up button and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.​
Start the LG Mobile Support Tool and click on Options -> Upgrade Recovery
{
"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"
}
It should now download the firmware (about 2gb) and flash it - this may take some time.
This is needed if you stuck in a bootloop after the flash is done:
Factory reset (this wipe your data and sdcard):
1. Turn the phone off.
2. Press and hold the Power and Volume down button.
3. When the LG logo pops up let go for a second and press the combo again.
4. You'll be prompted to press the Power button 3 times to wipe the device.​

I would hate to have to use this, but wow what a good find. Thanks for contributing.
Sent from my LG-D800 using Tapatalk 4

Just got my g2. About to root install twrp etc. This is exactly what I was looking for. Thanks for posting.
Sent from my LG-D801 using XDA Premium 4 mobile app

For anyone putting in dashes with the imei number, dont it wont work with em.

Just wanted to notify that this method made my 32gb D802 a 16 gb one!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.

x714x said:
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
Click to expand...
Click to collapse
I know it does'nt wipe data, but it reflashes recovery, and in my case something went wrong. But Lg DO sell D802 as a 16 gb model!

Can anyone using this method please post results. Just wondering if there is more success with this method as opposed to the other method. Thanks.

Saved my bacon today!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?

Noam23 said:
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Click to expand...
Click to collapse
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/

karstensson said:
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
Click to expand...
Click to collapse
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?

Noam23 said:
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Click to expand...
Click to collapse
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.

karstensson said:
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
Click to expand...
Click to collapse
Why should a password appear at that stage ???
If you went through all of the flash process successfully, booted successfully and only then did a factory reset (when you saw that password), I see no reason to blame the factory reset that you did. This is something to do with the flash process. Maybe this is kind of a punishment that LG unleash on those who use this process ? seriously, why on earth would anyone try to flash his LG2, if it wasn't to get rid of root ? I also don't understand how the password went away after you did hard-reset, since the device was "hard-reset" when you did that flash. You said that you re-flashed about 5 times, did that password appear after each of those 5 times ?

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
Same issue here.
I also got the question after I used the software to enter my encryptionkey. Wich I didnt have.
So I had to hardreset from the recoverymenu (volume down + pwr), then I suddenly had 10.77GB left instead of 26.77GB or something similar.
Annoys me pretty darn much at the time beeing!
I did use my IMEI, not my serialnumber and model. I'll try to use the serial and model this time around, and see if there are any differences at all in doing so.
And yes, it does say 32GB on the back. So we're not mistaken it for a 16GB-model
And it does say that the model is the 32GB when I check the hardware-info on the android itself.
Maybe this has something to do with me using the adbcommand for mounting storage incorrectly?
I thought however it would be reset when I used the LG Mobile Support Tool to hardreset everything though.

Will this work with the AT&T model D800?
Also does this remove all traces of root to the point where you get your warranty back?

what was the solution to this...

Does this work with the TMO versions?

The windows application keeps getting a Windows error and closing shortly after the process begins. Any tips?

I would prob stay away from this if i was anyone else....Because it must be messing people phones up and changing the storage capacity

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