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 ?

Root/TWRP/SD Fix/Init d/FlashPlayer/ADBlocking/debloating the SM-T900 / T900UEUAND4

Update 10/30/2014
There's no need to go back to the "B3" version any longer. The T900UEUANI1 is available on SamMobile, to be flashed w. Odin.
The cf-auto-root listed as "B3" on chainfire's site will work.
Note, I have not created any of this, please thank the original developers in their posts. This is simply a compilation of available info needed to have the most complete and working SM-T900, Samsung Galaxy Tab Pro 12.2.
The sole purpose is to make you save time. However, I'm not saying this will work, and it might even brick your device, but that risk is yours to take. However, it worked for me, so why shouldn't it... Trust the steps, there's a reason for this madness. Believe me when I say it; I've learned the hard way, and it has not been a pleasant journey.
If your SD cards looses necessary rw privileges it seems like not even a backup will correct them, even after wiping the SD cards and formatting data.
If you haven't yet upgraded from B3 to D4, I recommend you to do this first! There are major improvements between the two versions.
1. Rooting:
First flash the P900XXUANB3-RecoveryImg (forgetting this will create a softbrick, and you will have to start over, also use the Odin 3.07, supplied, I have not tested with the later 3.09)
then flash CF-Auto-Root-v2wifi-v2wifixx-smt900
for detailed method and files see: http://androidcentral.us/2014/05/root-galaxy-tab-pro-12-2-sm-t900/
I forgot, it's important to use original cables directly connected to the PC, a docking station connection, or an EOM cable might be a reason for flash failure.
2. install TWRP:
Flash openrecovery-twrp-2.7.1.0-v1awifi
link: http://forum.xda-developers.com/showthread.php?t=2679825
3. disable Knox:
Open SuperSU and answer yes to disabling KNOX
4. fix SD-card issue in KitKat 4.4:
Download and run JRummy's "SD KitKat Fixer" from market. I had no luck with any other comfortable fixing apps.
5. important!:
reboot into recovery and wipe both External and Internal SD, as well as Formatting Data. Don't forget to backup all files you want to keep onto your PC! for later re-installation. I know this must feel hard, but I sincerely advice you you follow this step. Most apps are not KitKat ready, as of now, and won't allow you to download or access the data if you haven't prepared your SD's in advance.
6. init d support:
Download and install Stericson's BusyBox from market
Download and install Uni-init v1.0
link: http://forum.xda-developers.com/showthread.php?t=1933849
7. Flash Player support:
Download and install fixed AdobeFlashPlayer 11.1
link: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-play-flash-video-android-4-t2548001
If you're using Dolphin Browser, also install the Dolphin JetPack, and modify Settings/Web Content/Flash Player/ to Always On.
8. ADBlocking:
Dowload and flash LATEST_MoaAB_ADBlocking_Super
link: http://forum.xda-developers.com/showthread.php?t=1916098
9. De-bloating:
for de-bloating at a maximum you can disable numerous of the Samsung apps, by pushing the three dots, upper right corner, while in the apps-screen mode.
Also, don't forget to un-check the de-bloated apps from auto-update in Play Store, as well as in the Samsung update if you signed up for this service.
10. (Re)-nstall your apps
You're done, and it's time to restore or download all the apps you need and it will work in KitKat 4.4
None of the modified stock ROM's currently available seem to mount correctly. If something goes wrong, you will most likely loose your SD card privileges. The original T900UEUAND4 stock ROM can be found here: http://www.sammobile.com/firmwares/3/?download=29102. Just unzip and flash with Odin, then start again with step 1.
Also, due to lack of time, I will not be able to monitor this post. I hope you will help one another out with clarifications, or anything I might have missed.
Best of luck,

Delete

Very nicely laid out. I've already done all this, but it's great to see a guide for new comers that may not know what to do. Thank you.

Thank you for the guide and gathering everything together. I just wanted to throw this out there, I followed the directions exactly....and I could not get mine to root. It would continually soft brick and a screen full of odd colors would come up every time. I read on the CF Auto Root thread that others had the same issue. One determined individual said he did it 10 times and it finally worked. Soooo....I continued to do it. And it finally worked, trying nothing different each time.
I tried 2 different computers, a win7 and win8, installed Kies to make sure drivers were there. Used official and another cable. I tried everything I could think of. In the end I would say as long as you're following the directions just keep trying.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
That's a link to the P900XXUANB3-RecoveryImg that my friend and I both used before getting root. Thanks again for the guide arcadia2uk!

So I was able to root and install TWRP but after an app caused some issues I went to wipe cache and brick. Flashed stock and had to do factory reset. However, I learned that attempting to restore a backup or wipe cache or do factory reset via twrp causes brick. Have to use Odin to flash back to factory. I also had to use the German region and lost my symbols on keyboard.
................edit..............
I updated kies and reinstalled all the drivers and flashed the cellular south firmware...All is well and current. Rooted, twrp, having fun.

Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
{
"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"
}
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!

deleted

robert1968 said:
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
Click to expand...
Click to collapse
The fix is actually put the m
Sent from my HTC One_M8 using Tapatalk

I don't know if it will help anyone else, but I just flashed TWRP 2.8 on my Galaxy Tab Pro 12.2 wifi with "D4" firmware using odin and it worked and I was able to make successfully a backup. Below is a link to the recovery I flashed. Of course your mileage may vary so do it at your own risk.
http://teamw.in/project/twrp2/244

The easiest way to debloat it is probably via titanium backup's batch mode actually.

Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2

saruba said:
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.

arcadia2uk said:
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
Click to expand...
Click to collapse
Yey! U R the man! Thanks so much it works flawlessly!
I think I have 2 different recovery files and they both doesn't work I don't know why I got them from twrp site... Anyways just to let you know I've done every thing with Odin 3.09 so yeah I'm confirming that it works fine.
Sent from my HTC One using Xparent BlueTapatalk 2

[Q] any rom for gty5363

There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.

bwizz60 said:
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
Click to expand...
Click to collapse
As far as I'm aware the 5363 is the o2 variant of the 5360
You might be able to just unlock the phone if not already unlocked (use galaxy toolbox) & flash 5360 firmware and use 5360 roms
Anything you do you do at your own risk - neither myself or xda are responsible for damage caused

I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead

bwizz60 said:
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
Click to expand...
Click to collapse
Why would you install cwm from rom manager? It's not supported - please do some searching and some reading else you will damage your device
There are two ways to get cwm on galaxy y
1- Flash temporary cwm zip in stock recovery - see http://d-h.st/u2m
2- Flash a kernel with cwm built in
If neither work on your variant you will need to flash 5360 firmware via odin at your own risk

I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.

bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Hi.
Here is the CWM link: http://forum.xda-developers.com/showthread.php?t=2649475
Please do some digging first before asking.
Also, ROM Manager is not supported on our phones, so do not use it.

bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Don't know what you are clicking on as it's a zip file
Make sure you are clicking on the right download button & not an ad - Install ad blocking software on pc or an app on phone if required
I never post exe files - all my files on dev host are Flashable zips/tars unless otherwise stated
See below Screenshot - Just press the download button as shown in Screenshot
{
"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"
}
Also you should take note of what you are reading, where you are reading it & what device it relates to - rom manager has never been a compatible way of flashing cwm on a galaxy y

The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that

bwizz60 said:
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
Click to expand...
Click to collapse
It would only say 5360 if you flashed 5360 firmware via odin
Iv kept telling you if you want to use 5360 kernels you will probably have to flash 5360 firmware
Feel free to do what you want at your own risk

Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick

bwizz60 said:
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
Click to expand...
Click to collapse
With respect Iv told you both ways to get into cwm
With the temp zip I provided by Flashing in stock rom or by Flashing a kernel with cwm built in
You have chosen to ignore all what I'm telling you & trying to do things in unconventional ways - Therefore I can no longer offer you support
Just flash stock rom via odin

I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative

bwizz60 said:
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
I said to use galaxy toolbox to unlock your phone - ie remove network sim lock if your phone is locked to a specific network
At no point did I say use it to flash cwm
If you can't get into recovery you need to flash stock rom via odin
I do have alot of patience but I find it annoying when people don't read things properly especially when the answers have already been written for them

I do appreciate your help. I am now following the odin info "supplied by yourself on the site"
Ta

bwizz60 said:
I am now following the odin info "supplied by yourself on the site"
Ta
Click to expand...
Click to collapse
That sounds sarcastic...
FYI, this Odin info can be found in his signature. It is also a sticky in the Android dev section.
Search, search, search.
bwizz60 said:
I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
u wot m8
If you don't know what you're reading when it's filled with seemingly bizarre terminology (we've been at that stage one time or another), you do three things:
1) Read on and/or use Google.
Usually definitions will pop out after a while. If I'm not mistaken there are a few threads outlining terminology definitions and usage.
2) Follow everything that they say. And when I say follow, I mean follow 100%, by the book. Reread the instructions over and over to make sure you are actually doing it right.
3) PM another more well-informed member, and don't be afraid to ask.
As for patience, well...
He has dealt with countless people that were in about the same situation as you: thinking that they knew what they were doing and eventually getting into deep s**t with no way out. He has always tried helped them out. Problem is, some of them simply don't want to listen, even if he was correct (which he most likely was). Even then, he tries his best.
Trust me, he knows what he's doing.
Take a deep breath, reread EVERYTHING on this thread, and restart from square one: stock ROM.
If you're too lazy to find (I hope you're not) here is the link for Odin:
http://forum.xda-developers.com/showthread.php?t=2568853
Risky, but everything here is a risk, isn't it? I rarely hear of 5363 users getting stuck here, so this should be fine.
Good luck.

Why would I be sarcastic? there is volumes of stuff on the site all done by this guy.! I show appeciation of this . I can assure you I do spend hours trying to follow information. Some of the links don't work ,sometimes my Firefox security stops progress . very frustrating at times;.

Thanks Mr Smith, now unbricked. I could not find odin 3.184 "spent over an hour trying" 1.85 worked ok . Phone now wakes up as 5360! If the rom is less bloated than the 02 one .I might leave well alone! Stress level falling!

What he meant was Odin3 v1.84.
But, its nice to see things sorted out with your partner's phone.

I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!

bwizz60 said:
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
Click to expand...
Click to collapse
Root phone
Use Link2sd (playstore) to uninstall system apps
Use the temp cwm I posted a few pages back - place on root (not in any folder) of sd card & flash in stock recovery to get to cwm
Or use a custom recovery that has cwm built in eg hells fusion #50 for stock based roms
Can't give you any more support with this as I'm just repeating what Iv already said

[Q] A Root Gone Wrong!?!?!

Hi Guys,
I am really freaking out right now since I did apply a root to my SMT530NU Samsung Galaxy Tablet, everything went well, but then the major components of the tablet like the WiFi starting going haywire. I can't seem to play videos anymore in web browsers, and I don't have a steady connection to play games on it anymore. I used ODIN with the CF Auto Root to Root this Tablet. It is not my router for sure. Every other computer in the house works fine.
Can someone give me assistance?
ASAP is preferable.
Thank you guys so much :'(

AndroidDR01Ds said:
Hi Guys,
I am really freaking out right now since I did apply a root to my SMT530NU Samsung Galaxy Tablet, everything went well, but then the major components of the tablet like the WiFi starting going haywire. I can't seem to play videos anymore in web browsers, and I don't have a steady connection to play games on it anymore. I used ODIN with the CF Auto Root to Root this Tablet. It is not my router for sure. Every other computer in the house works fine.
Can someone give me assistance?
ASAP is preferable.
Thank you guys so much :'(
Click to expand...
Click to collapse
Lollipop or kit Kat and are you prepared to lose stuff like app data (just answer honestly, it helps me know which fix to recommend)

thisisapoorusernamechoice said:
Lollipop or kit Kat and are you prepared to lose stuff like app data (just answer honestly, it helps me know which fix to recommend)
Click to expand...
Click to collapse
Uh Kit kat, I already did a complete system wipe.

AndroidDR01Ds said:
Uh Kit kat, I already did a complete system wipe.
Click to expand...
Click to collapse
Oh cool hopefully that'll make things easier. I would recommend flashing the firmware file through Odin to really reset everything (do a factory reset in recovery first)
Wait before you touch these files let me know if you're Canadian, these are USA builds. Still compatible, just thought you'd like to know
Kit Kat firmware file
Lollipop firmware file
Since you're starting kit Kat either should be fine just do a factory reset first then flash whichever one you want through Odin then I'll tell you the proper way to root

Alright. I should be back here in about 15 minutes TOPS. Thank you so much in advance!
Well I am in the USA. But yes everything makes a difference to me

AndroidDR01Ds said:
Alright. I should be back here in about 15 minutes TOPS. Thank you so much in advance!
Click to expand...
Click to collapse
No problem. Just making sure, in Odin, select the firmware with the AP button ( might be labeled PDA in some older versions)
Like so (remember to make sure repartition is NOT selected):
{
"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"
}

So I am currently on ODIN, I just put it onto PDA and clicked Start.
(I am using the Lollipop file)

Alright, so it is done flashing. It has booted up a very fineeeee looking firmware heh (Lollipop)
So the wifi should be fixed now? I hope so. I'm going to check. But for the process on rooting..?
YES INDEED THE WIFI IS BACK!

AndroidDR01Ds said:
Alright, so it is done flashing. It has booted up a very fineeeee looking firmware heh (Lollipop)
So the wifi should be fixed now? I hope so. I'm going to check. But for the process on rooting..?
Click to expand...
Click to collapse
Wi-Fi should be OK now that's what the Odin file is for. If you can wait like ten minutes I'll give you a nice simple guide to root the proper way

Alright, I will wait. -Gives a thanks-

AndroidDR01Ds said:
Alright, I will wait. -Gives a thanks-
Click to expand...
Click to collapse
And I'm back, sorry about that, here we go. Brief overview, we're going to install TWRP custom recovery and from there install superSU, I did this exact method with no issues.
First you're going to need two files, one saved to your PC, one to your tablet. On this thread click the download button, then matissewifi > twrp > openrecovery-twrp-2.8.6.0-matisse.tar (important, you need the tar file not the img file), this obviously is the recovery file and needs to be saved to your PC. Then go here and download the zip file and save to your tablet.
So you're going to flash that recovery file through Odin, AP button like last time, BUT make sure auto-reboot is NOT selected (again, make sure re-partition is NOT selected either). So now when it's done the tablet won't reboot, this is good, just wait 5-10 seconds after the status bar says it's done and unplug it and power it off. You're going to want to boot into TWRP recovery with power, home, vol+ (absolutely necessary this be done before rebooting normally), and install that superSU zip. Then you can reboot normally. Make sure to run the superSU app and follow any prompts it has for you.
Let me know if anything is unclear before trying it.
(Sorry typing on my phone with slightly broken screen is hard, at my buddy's place and forgot my tablet of course)

thisisapoorusernamechoice said:
And I'm back, sorry about that, here we go. Brief overview, we're going to install TWRP custom recovery and from there install superSU, I did this exact method with no issues.
First you're going to need two files, one saved to your PC, one to your tablet. On this thread click the download button, then matissewifi > twrp > openrecovery-twrp-2.8.6.0-matisse.tar (important, you need the tar file not the img file), this obviously is the recovery file and needs to be saved to your PC. Then go here and download the zip file and save to your tablet.
So you're going to flash that recovery file through Odin, AP button like last time, BUT make sure auto-reboot is NOT selected (again, make sure re-partition is NOT selected either). So now when it's done the tablet won't reboot, this is good, just wait 5-10 seconds after the status bar says it's done and unplug it and power it off. You're going to want to boot into TWRP recovery with power, home, vol+ (absolutely necessary this be done before rebooting normally), and install that superSU zip. Then you can reboot normally. Make sure to run the superSU app and follow any prompts it has for you.
Let me know if anything is unclear before trying it.
(Sorry typing on my phone with slightly broken screen is hard, at my buddy's place and forgot my tablet of course)
Click to expand...
Click to collapse
Sounds good, ill try it out right now.

Okay so I've gotten it down. TWRP threw me off a bit since i never used it but I hit install and directed myself to the SuperSU apk zip file and installed it, rebooted. So now im in with the prompts for SuperSU's binary updates, and its asking if I should do Normal installation or TWRP/CWM-based installation.

AndroidDR01Ds said:
Okay so I've gotten it down. TWRP threw me off a bit since i never used it but I hit install and directed myself to the SuperSU apk zip file and installed it, rebooted. So now im in with the prompts for SuperSU's binary updates, and its asking if I should do Normal installation or TWRP/CWM-based installation.
Click to expand...
Click to collapse
Normal works best just be patient takes up to a minute or two

thisisapoorusernamechoice said:
Normal works best just be patient takes up to a minute or two
Click to expand...
Click to collapse
Alright, that seems to about do it. Thank you for the fix! :good:

AndroidDR01Ds said:
Alright, that seems to about do it. Thank you for the fix! :good:
Click to expand...
Click to collapse
Always glad to be able to help :good:

Marshmallow 6.0 on a SM-J320FN?

is this possible? i can't seem to find anywhere to download/flash the OS? but i am new to this, so maybe lookingp in the wrong places.
any help gratefully received!

secretmachines said:
is this possible? i can't seem to find anywhere to download/flash the OS? but i am new to this, so maybe lookingp in the wrong places.
any help gratefully received!
Click to expand...
Click to collapse
Ok, It seems like you need help!
So J320FN isn't getting Marshmallow, but there are what we call in XDA and anywhere else, Custom ROMS!
Now this practically optimizes your device for better performance, along with a newer version of Android!
When you searched for your device (SM-J320FN) you probably found LineageOS.
LineageOS is a Custom ROM for a big variety of devices.
Now for the J320FN we have LineageOS 13.0 (Marshmallow) and LineageOS 14.1 (Nougat), while have LineageOS 15 (Oreo) in the works thanks to our crew including the Main dev, djeman.
Now to flash Custom ROMS you need a recovery which you flash via Odin.
Then copy the ROM zip to the SD or Device storage.
Boot into recovery by holding VOL. UP+POWER+HOME at boot.
Wipe Dalvik Cache, Cache, Data, Internal Storage (If you put ROM on SD) and System.
Then Flash the ROM with Gapps (Google Apps, Such as Play store...)
Wait and Reboot

Diamond26 said:
Ok, It seems like you need help!
So J320FN isn't getting Marshmallow, but there are what we call in XDA and anywhere else, Custom ROMS!
Now this practically optimizes your device for better performance, along with a newer version of Android!
When you searched for your device (SM-J320FN) you probably found LineageOS.
LineageOS is a Custom ROM for a big variety of devices.
Now for the J320FN we have LineageOS 13.0 (Marshmallow) and LineageOS 14.1 (Nougat), while have LineageOS 15 (Oreo) in the works thanks to our crew including the Main dev, djeman.
Now to flash Custom ROMS you need a recovery which you flash via Odin.
Then copy the ROM zip to the SD or Device storage.
Boot into recovery by holding VOL. UP+POWER+HOME at boot.
Wipe Dalvik Cache, Cache, Data, Internal Storage (If you put ROM on SD) and System.
Then Flash the ROM with Gapps (Google Apps, Such as Play store...)
Wait and Reboot
Click to expand...
Click to collapse
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
My Pleasure :fingers-crossed:

so i think the developer setting was turned off and i started to get the FRP lock problem.
i managed to use Odin to reinstall Android, but it is now stuck in bootloop.
i've installed Kies3 and Smart Switch, but neither recognise the handset (not compatible), so i can't reinstall firmware, etc.
i'm kinda stuck... help!

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
Im currently on a J320FN with a stock 5.1 rom (manually updated via sammobile) but have instead done the following :
1. Got a good Android kitchen (A bash/shell program that makes creating roms easy as could be) I woukd suggest SuperR's Kitchen due to it being the most updated one. On XDA portal?
2. Downloaded the firmware i want from sammobile.
3. Debloated the rom (option in the kitchen to remove unwanted apps from system/app or system/priv-app) making space.
4. Added Supersu (again the kitchen walks you through all the options for rooting the rom).
5. Added my own apps to run as system (such as adaway or nova launcher to replace TouchWiz)
6. Created the rom and flashed the zip.
Now im on partitioning the system block in order to save 2gb of space i dont need since the new system is 780mb from 1.9gb..
Both ways are good and safe / stable if you are careful, it's just that one provides updates and sources and build threads (LOS) , the other is a great and fun way to learn more about android and rom building plus you get to have it 100% YOUR WAY.. With building your own rom using the kitchen you can even go as far as editing the settings apk to rearrange the options or add ur own... And many more thing to discover...
Good luck no matter what you choose to take from this wonderful community!
Peace

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
I tried it for the same reason and it turned out to be a mistake. The rom I tried (Lineage 13) is full of display bugs. Now I lost my original firmware and probably voided the warranty. Your best bet is just to move your apps to the SD card instead

idklol123 said:
I tried it for the same reason and it turned out to be a mistake. The rom I tried (Lineage 13) is full of display bugs. Now I lost my original firmware and probably voided the warranty. Your best bet is just to move your apps to the SD card instead
Click to expand...
Click to collapse
Your warranty is void, im sure Lineage OS has the appropriate notice about this..
Yiu could seek help about your issue, perhaps there is something along the lines that you missed.. Wiping dalvik and or cache and re trying it could help..You should always do a nandroid backup using twrp or cwm recovery or even Titanium Backup / My Backup Pro. It is something that you should practice since you're messing with any type of software and hard-flashing firmware.
Again, consider a stock rom with root and xposed module, a partitioned system block and deodexed apks..
You can get firmware releases for your country and carrier from sammobile.com anfd flash it via odin. That should give you OTA updates and stock stability...
Peace

Kaiyum said:
Im currently on a J320FN with a stock 5.1 rom (manually updated via sammobile) but have instead done the following :
1. Got a good Android kitchen (A bash/shell program that makes creating roms easy as could be) I woukd suggest SuperR's Kitchen due to it being the most updated one. On XDA portal
2. Downloaded the firmware i want from sammobile.
3. Debloated the rom (option in the kitchen to remove unwanted apps from system/app or system/priv-app) making space.
4. Added Supersu (again the kitchen walks you through all the options for rooting the rom).
5. Added my own apps to run as system (such as adaway or nova launcher to replace TouchWiz)
6. Created the rom and flashed the zip.
Now im on partitioning the system block in order to save 2gb of space i dont need since the new system is 780mb from 1.9gb..
Both ways are good and safe / stable if you are careful, it's just that one provides updates and sources and build threads (LOS) , the other is a great and fun way to learn more about android and rom building plus you get to have it 100% YOUR WAY.. With building your own rom using the kitchen you can even go as far as editing the settings apk to rearrange the options or add ur own... And many more thing to discover...
Good luck no matter what you choose to take from this wonderful community!
Peace
Click to expand...
Click to collapse
This is the best thing i heard so far!
I was looking for this. I like the UI of Samsung, and it was stable and fast for me for daily usage. Had some bad experiences with LOS and RR so i was thinking of re-flashing stock, then rooting and then removing system apps. The only issue i have is too little free space. Is the effect same if i do that compared to your method? Can you tell me what happened to your little experiment? How much free space do you have?
Can i flash your modified rom and get it to work on my phone?

hi everyone, sorry to ask again, i seem to be going round in circles! can anyone advise the next step?
- i installed lineageOS ok, but must have accidentally turned off OEM Unlock, so am now getting "Blocked by FRP Lock
- i reinstalled a version of original firmware, but that is getting stuck in bootloop
- i've tried reinstalling original firmware downloaded from sammobile, with Odin, but that fails
- i've installed Kies and Smart Switch on my PC, but both say the handset is not supported, so I can't install firmware that way
what should i try next?

djaneski said:
This is the best thing i heard so far!
I was looking for this. I like the UI of Samsung, and it was stable and fast for me for daily usage. Had some bad experiences with LOS and RR so i was thinking of re-flashing stock, then rooting and then removing system apps. The only issue i have is too little free space. Is the effect same if i do that compared to your method? Can you tell me what happened to your little experiment? How much free space do you have?
Can i flash your modified rom and get it to work on my phone?
Click to expand...
Click to collapse
Im sorry im replying so late,given your post i take it you need some help...I wont go big here and tell you i can fix exactly what you want,however i have managed to get it all working besides repartitioning the mmcblk0!
Im out of town during weekends for work but i can possibly have a rom ready for you by Monday night (GMT+2).
I will still recommend you download SuperR's Kitchen (if possible the donate version)and start cooking your own rom,the kitchen provides 100% j3xnlte and j3 variants!
You WILL need to download the firmware i will point you to for the modem but its for better use also,you can run the stock for a while and then flash (mine or your own) the debloated/deknoxed/lighter version.
About the space,i have attached a SS from my Smart Manager..I have magisksu,magisk-xposed,iYTBP,gapps pico + photos,swiftkey replacing Sammy Keyboard and nova launcher replacing TW..FFox,Yahoo Mail,TiBu,Lucky Patcher and Facebook / Messenger...Some i have placed as system apps and others preinstalled as user apps (such as Busybox and Telsa Unread or Adaway that don't work correctly when placed in /system/app)..
Still i have Airdroid moving files locally and have at least 600mb of romzips being moved all the time while flashing....
That 5.1Gigas you see are 100% usable for me because i can swap system and data apps to my liking...also trust me,if you have relationship issues with googke,debloated roms come down to 1/3 of original size...
Let me know what i can help with,have a blasting weekend!
Peace
{
"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 the depths of outer space using highly potent telepathically altering mushrooms.
---------- Post added at 09:45 PM ---------- Previous post was at 09:31 PM ----------
secretmachines said:
hi everyone, sorry to ask again, i seem to be going round in circles! can anyone advise the next step?
- i installed lineageOS ok, but must have accidentally turned off OEM Unlock, so am now getting "Blocked by FRP Lock
- i reinstalled a version of original firmware, but that is getting stuck in bootloop
- i've tried reinstalling original firmware downloaded from sammobile, with Odin, but that fails
- i've installed Kies and Smart Switch on my PC, but both say the handset is not supported, so I can't install firmware that way
what should i try next?
Click to expand...
Click to collapse
Download TWRP if im not mistaken by djeman and flash that through odin!That passes just make sure to UNTICK auto reboot so you can reboot to recovery after removing battery(or just ignore the unticking if ure d
fast enough to hold vol up + home + pwr while the flash resets)
Wipe system,dalvik,cache,data and reboot...
Sent from the depths of outer space using highly potent telepathically altering mushrooms.

My gf got this phone for Christmas, it's 2017 why are (many) retailers selling a phone that is still on Android 5.1?..