Develop Bugs

[Guide] Root and CWM recovery new ICS.

To start, you will need
Recovery-cmw-hercules.tar (doesn't have to be the latest, you can update it later). This can be found in other recovery threads, as the process remains the same.
Odin3 v1.85 (or any other compatible version)
root.zip found Here
Steps:
1) Make sure Kies is exited, and you have the drivers installed for Odin. If not, check the other threads as this has been covered many times
2) Just select your CWM recovery for PDA once you are in DL mode (which is achieved by holding down VOL Up and VOL Down when the phone is off as you plug in the cable). Select vol up to confirm dl mode.
3) In Odin, leave the default boxes (Auto reboot and F. Reset time), and then select PDA and choose the .tar file we found earlier. Make sure odin sees your phone properly and start this!
4) once you have CWM recovery installed copy the root.zip to your sd card, and boot into CWM recovery. Do a Nand Backup and then install root.zip and enjoy!
5) Delete that crappy bloat!
For those having connection issues in Odin, try the following.
1) Exit Kies
2) Change to a different USB port
3) Reinstall your USB drivers.
I kept getting an error, and the above fixed that.

Thank you!

Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA

Thanks a lot for posting this for everyone. Hopefully this will quell the 50 billion requests that could be handled by using search or google.

TheTechNiq said:
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
Its should work the same, my official tmo 4.03 ics
was just rooted doing this

so it's the same process?

Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)

Teo032 said:
so it's the same process?
Click to expand...
Click to collapse
Yes but make sure you download the root.zip file OP posted a link to.
Once you're done with the odin part, having the recovery-cmw-hercules .tar all done.
You should see CWM rom manager in your app, you can click on it but cant really use it. because you don't have superuser permission, That why you need to copy the root.zip file to your sd card. Now get in to CW recovery by turning off the phone.
hold vol. up+down,and hit the power on button, scroll down and install the root zip.
then reboot. now you should have superuser permission and can now uninstall, or freeze all the junk with Titanium backup.

kwilsonjr said:
what do you mean 'leave the default boxes'?!? leave them checked? leave them unchecked? leave them alone? what? I'm assuming you mean leave the boxes alone (default).
Click to expand...
Click to collapse
Don't touch anything but the PDA button, select the .tar file, and click start.
For those worried about using the GB root process with the new ICS ROM, the Kies flashing does not put a new recovery on it. It's the same one that shipped with your phone. Therefor overwriting the the recovery with CWM 5.0.2.6 (via Odin) is the exact same. The root.zip flashed from VWM just installs su, busybox, and the superuser.apk into the OS, this has been done on many ICS roms already.
TL;DR: the process is identical, and confirmed working.

Rooted! T989 with Stock ICS update!
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!

ResidentJack said:
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
Click to expand...
Click to collapse
Busybox is included in the root.zip in this post?

Worked like a charm thanks!

Damn... Stuck on "Goodbye"
Ok, so I rooted and it worked perfectly, only problem is I'm now getting stuck on "Goodbye" screen when shutting down, or when restarting. I have removed the battery for 2 minutes, wiped cache, wiped dalvik...
Still the same thing...
Anyone have any ideas?
Thanks

kwilsonjr said:
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OK. Don't know what the heck is going on. Closed and re-opened odin 5 times and tried each time. It finally took on the 5th try. weird.
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/007> Added!!

What did you guys use to remove all the bloatware?

n/m found it.

Blackleopord187 said:
What did you guys use to remove all the bloatware?
Click to expand...
Click to collapse
I freeze it with titanium backup.

I can confirm the reboot hang issue.

ian577416 said:
I can confirm the reboot hang issue.
Click to expand...
Click to collapse
maybe its an isolated incident on some devices? (I used the OP's root method) I just tried restarting and turning off my phone and i get no hangs on the goodbye screen or anything.

No hang issues here. Root method works great.
Bloat removed,,,,,ALL OF IT!!!!!

PIT file for Note 3 Neo N7505 for non-HK roms

I've tried different ROMs from samfirmware, but the only one I could successfully install via Odin are the Hong Kong N7505ZH versions. Based on the Odin error message it seems this is because of invalid partition sizes. I wanted to re-partition the device, but couldn't find any PIT files for the N7505XX versions. I've seen that it is called HLLTE_EUR_OPEN_4G.pit or HLLTE_EUR_OPEN_4G_hidden30M.pit but didn't find a download link for them anywhere.
Does anyone have these handy, or could someone extract the PIT from their device?
EDIT: it looks like they can now be downloaded from various places on the internet. I have uploaded them here for anyone in need. Tested both, and they don't void your KNOX warranty so the signature in them seems perfectly legit. The zip file contains both HLLTE_EUR_OPEN_4G.pit (for Hong Kong roms) and HLLTE_EUR_OPEN_4G_hidden30M.pit (for European roms). It looks like you'll need the latter one for most of the 4.4.x and the new 5.1.1 ROMs found on samfirmware

sztupy said:
I've tried different ROMs from samfirmware, but the only one I could successfully install via Odin are the Hong Kong N7505ZH versions. Based on the Odin error message it seems this is because of invalid partition sizes. I wanted to re-partition the device, but couldn't find any PIT files for the N7505XX versions. I've seen that it is called HLLTE_EUR_OPEN_4G.pit or HLLTE_EUR_OPEN_4G_hidden30M.pit but didn't find a download link for them anywhere.
Does anyone have these handy, or could someone extract the PIT from their device?
Click to expand...
Click to collapse
this you would:
http://asanfile.com/file?path=samsung/Flash File/SM Series/SM-N7505/

fabien13121976 said:
this you would:
http://asanfile.com/file?path=samsung/Flash File/SM Series/SM-N7505/
Click to expand...
Click to collapse
I don't think that's site repuable enough for me to spend money on downloading a 3kb large file

desolated I thought it was enough to register and that it was gratuit.Mes excuses.

any luck?
also, it's on these two places, but ..
http://filesgsm.com/showthread.php?3920-N7505
.. you can register here, but can't DL attachments without paying:
( http://filesgsm.com/showthread.php?3677-How-to-download-attachments )
.. and here
http://www.gsmforum.su/showthread.php?t=98783&langid=1
.. but you need to have five posts plus they need to be confirmed to be constructive,
I wrote some, but my Russian is not up to the task.
Please share any progress here, hopefully we'll find it soon

Pit file of my n7505:
https://mega.co.nz/#!VVEDES6a!RFerFOnv0eOkCMZyHPqUid0HeS1t2nU28sSG3r--tvU
I followed this post to create pit file:
http://www.htcmania.com/showthread.php?t=823064
Note: new profile for n7505 must be create or you can use mine (link to mega)

m80dv said:
Pit file of my n7505:
https://mega.co.nz/#!VVEDES6a!RFerFOnv0eOkCMZyHPqUid0HeS1t2nU28sSG3r--tvU
I followed this post to create pit file:
http://www.htcmania.com/showthread.php?t=823064
Note: new profile for n7505 must be create or you can use mine (link to mega)
Click to expand...
Click to collapse
Thanks a lot, I'm gonna test it tomorrow to check if it's fine. I'll also make a copy of my own to check what differences are.

m80dv said:
Pit file of my n7505:
https://mega.co.nz/#!VVEDES6a!RFerFOnv0eOkCMZyHPqUid0HeS1t2nU28sSG3r--tvU
I followed this post to create pit file:
http://www.htcmania.com/showthread.php?t=823064
Note: new profile for n7505 must be create or you can use mine (link to mega)
Click to expand...
Click to collapse
I extracted my own pit using heimdall, and compared it to yours. It seems they are exactly the same... Did you manage to update your FW to any official non-HK roms or 4.4.2?

Meanwhile I could update to 4.4.2. hidden.img was of course broken, but creating a new .tar file which only contained recovery.img was enough to remove the firmware upgrade failed flag (and it also passed the new 4.4.2 secure bootloader checks), so I could boot into the new OS and I didn't see any visible errors after the update.
Having a proper install without failures would be better though...

Bootloop after Re-Partition
sztupy said:
Meanwhile I could update to 4.4.2. hidden.img was of course broken, but creating a new .tar file which only contained recovery.img was enough to remove the firmware upgrade failed flag (and it also passed the new 4.4.2 secure bootloader checks), so I could boot into the new OS and I didn't see any visible errors after the update.
Having a proper install without failures would be better though...
Click to expand...
Click to collapse
Hello.
I´m a bit newby in this area, but so brave to soft brick my N7505 Phablet
I´ve downloaded your Pit file --> "Can´t write it here" , and via Odin 3.09 I´ve installed a samfirmware Spanish ROM: N7505XXUANB4_N7505PHEANB2_N7505XXUANB4_HOME.tar.md5
My inexperience have make me think that I´could use this ROM with your Pit file and select the Flags: Auto Reboot, Re-Partition, F Reset Time. But at the end of the procedure the Screen have begin flashing with color points :silly:
After 5 mitutes Ihave reset the mobile but it goes right to Download Mode.
There is down the Odim conf window.
Any idea to solve this problem? Now I´m really Frighten, and almost I did not do a backup before.
Thanks in advance.
ED: I´ve try using a newest PHE ROM, but after 1 second , the system don´t go ahead (Here is the Odin message) not Re-partitiion:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7505XXUCNG5_N7505PHECNG1_N7505XXUCNG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!

i'm from india is that file support for my Samsung Note 3 Neo I want to flash Official Firmware !

Just re-partitioned my phone with HLLTE_EUR_OPEN_4G_hidden30M.pit, and so far it works perfectly. I could finally install the latest roms error free from Odin. KNOX warranty status is still okay, so no issues with the signature of the file. File links in first post if anyone needs it.

Note, that the HLLTE_EUR_OPEN_4G_hidden30M.pit file works just fine for the new 5.1.1 Lollipop ROMs as well

Can someome explain what is this Pit file do?

help me for sm-n7505 pit file for update to 5.1.1
sztupy said:
Note, that the HLLTE_EUR_OPEN_4G_hidden30M.pit file works just fine for the new 5.1.1 Lollipop ROMs as well
Click to expand...
Click to collapse
Hello. When I update sm-n7505 with odin, I encountered the following error. And to solve it I realized that I do have to file Pitt Operation re-partition. Pitt files that I've put in the link below. However, since I want to update Android 5.1.1 Do you think I use this file or files (HLLTE_EUR_OPEN_4G_hidden30M.pit)
eror :
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N7505XXUDPF1_N7505PHNDPF1_N7505XXUDOK4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
boot.img
recovery.img
system.img
modem.bin
cache.img
hidden.img
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
..............................................................................................................................................
and links :
tsar3000.com/Joomla/index.php?option=com_content&view=article&id=659it-and-ops-files-for-samsung-android-mobile-phones&catid=55:samsung&Itemid=82
4shared.com/rar/VdQ-yAaqba/SM-N7505_HLLTE_EUR_OPEN_4G.html
very thanks.

s4 mini won't boot

I have a Samsung S4 Mini on the Verizon network (SCH-i435). I restarted my phone this morning and it took a much longer than usual to boot. My screen showed the Verizon logo for about 5-10 minutes and when the phone finally booted I was greeted with the utility to set up the phone (pick language, setup email, etc. etc.). I was confused because I had done this already a few months ago when I bought the phone. I skipped the steps and I was greeted with the stock home screen (all my custom shortcuts and widgets were gone). All my marketplace apps were still installed, but some of them had been reset (had to reconfigure waze, winamp, etc). My best guess is that there was an OTA update or some security patch that reset everything. Finally I got things running again the way I liked them. I was using my phone and suddenly it went dead. I tried to restart it but nothing showed on the screen. Oddly enough the phone just vibrates over and over again, but the screen remains black. No matter what I do I can't boot it. The only way I could stop it from vibrating was to pull out the battery. Is there any hope to recover this phone? Thanks.

Did you try to enter recovery mode?

Yes, I followed the instructions on the manufacturer site. I held down the home button, up volume, and powered the device on. A small bit of text appeared for a split second, it was so fast I couldn't read it. It disappeared and the screen went black and the same vibrate pattern started up again.

I got a video camera and managed to capture the text that was being displayed. Here is a screenshot...
It looks like...
MMC: mmc_read fail
Movinaand Checksum Confirmation Fail
Any hope of fixing this?

I asked for recovery cause it was easier to reset to factory the phone. If that's not working, i don't know if there's hope for it to enter download mode, for manual flashing with odin.

I'm able to get into download mode. Is there a ROM I can flash with? This S4 Mini is the Verizon phone so it is the SCH-i435, I didn't think there were any custom roms I could use with this phone.

Stock rom.
Try http://www.sammobile.com/firmware and see if your firmware is there.

Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.

RoyaLKurTx3 said:
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
Click to expand...
Click to collapse
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?

droid2501 said:
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
Click to expand...
Click to collapse
I am not sure since this is the first time for me with experience with that phone...
In Odin, make sure Auto Reboot and F. Reset Time check boxes are only two that are selected. DO NOT SELECT ANY OTHER OPTION! Click the AP/PDA button and select that file you downloaded earlier with extension I435VRUBNE1_I435VZWBNE1_VZW.tar.md5 Click the CSC button and select file with CSC in its name. Ignore if there is no such file. Click the PIT button and select the .pit file. Ignore if there is no such file. (You should have this file, do it if you are having that error) Now, once you are ready, hit the START button to begin the flashing process.
If you have any other problems please ask.

RoyaLKurTx3 said:
(You should have this file, do it if you are having that error)
Click to expand...
Click to collapse
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.

droid2501 said:
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
Click to expand...
Click to collapse
The file should be one of the extracted files in the file you have downloaded from my links. If the file is not there, then most probably Verizon modded the phone to not be able to flash via Odin Mode.
The error during the update may have happened because of low battery, making your phone shut down during the update, which is serious.
You can check yourself if your phone is under warranty (excluding the warranty period)
-Just go to download mode and you will see: KNOX WARRANTY VOID: [if it is 0x0, than it you are still under warranty, but if it says 0x1, you are not.]
Yeah, you should go to the place you have bought the phone from, if none of the above steps worked for you.
Good Luck.

I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?

droid2501 said:
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
Click to expand...
Click to collapse
You got the same version of your previous phone?

Yes, that's all they would do for free. They did offer me a Droid Turbo for and extra $100.00 but I really don't like the large phones they're coming out with these days so I declined.

Then you shouldn't get OTA Updates. I don't think that it was needed since the problem you got earlier was because of a faulty firmware from Verizon, which is unlikely or your phone had no battery while your phone was updating.

SM-T211 wifi + bluetooth not working after root and bloatware removal

Hi all, new guy to the forums. After rooting my T211 (4.1.2) via Odin and with TWRP and SuperSU, I started to remove some of the bloatware that Samsung sticks on the tabs. everything was working great until I rebooted one day and then the wifi and bluetooth stopped working. I've flashed the 4.4.2 in preperation to flash a custom rom, but it seems no matter what I do, the wifi and bluetooth issue remain. Can anyone help me with a zip to reinstall the wifi and bluetooth? or an instruction on how to do it? I have the 4.1.2 rom as well as the kitkat rom from italy and a few custom roms. If I knew how to make a flashable zip and which apks and such to use I would be happy to do it myself. Any help would be greatly appreciated. Thanks in Advance, James.

Bump
Bump

Tried just re flashing stock nonrooted bloated os back on?
---------- Post added at 03:41 AM ---------- Previous post was at 03:41 AM ----------
With odin of course and use the pit file for a full reformat wipe

Flashing stock rom
Trying it now. I'm a bit of a idiot, when I was trying to flash the stock rom, I forgot to unzip and wondered why I was getting an error...haha. I wanted to try a dirty flash just in case it worked but no kewpie doll. Trying it with the pit file now. fingers crossed.

Ugh...no luck. here's the read out from Odin. Not sure whats going wrong yet. Maybe not the right pit file.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T211XXAML1_T211OXXAML2_T211XXAML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Yea double check the pit file is for your model tablet

LT02.pit, this is the one that keeps getting reccomended in all the posts I've read. Says its for the T210 but it is supposed to be the same?

This is very frustrating thought I had it fixed. Wifi button turned on...bluetooth button turned on...just kept scanning. then both shut off and wont stay on

So after reflash they still do it?

yeah, they still do it. puzzling that it turns on but only scans and has no connection.

Using a file manager with root access, delete the following 2 directories:
/data/misc/bluedroid
/data/misc/wifi
Then, reboot.
Can't promise it will work, but it may.

Cool, gonna give it a try in a bit.

Any luck?

well, yes and no... after loading up root browser, I navigated to /data/misc. I don't have a bluedroid directory. I have a bluetooth and a bluetoothd and I have a wifi and a wireless directory. I deleted the first three and rebooted. I then was able to turn on the wifi and it recognized my router and connected...for about 10 seconds then shut off again and wouldn't turn on again. So, I think we're on the right track but not quite there yet. The fact that it did work even if temporarily was encouraging.

If it were me, I would go to sammobile.com and download the full firmware package for your region and flash it with Odin. That will ensure that you have a matching set of firmware (boot, radio, system, etc.) It will not wipe your data. If it works correctly after that, then you can reinstall your custom recovery and whatever rom you want.
Sent from my SM-G920V using Tapatalk

well, that didn't work either. Still has the same problem. I went into twrp and wiped everything except the external sd card. then with Odin, flashed 4.1.2 rom for UK and wifi will not turn on. Scratching my head now

Any other ideas?

Try using Heimdall with a full firmware package. You'll have to extract the firmware package (change the filename ending with ".tar.md5" to ".tar" and use 7-zip to extract it.
Then open up Heimdall, go to "Utilities -> Download PIT -> Destination File" and pick a location and name for the pit file.
Following this step, go to "Flash -> Options -> PIT" and browse to the pit file.
You will then have to go through the process of adding each partition that you want to flash, browsing to the location of the firmware package, and then flashing it.
I've done this several times, although I have not tried with "Repartition".
You will probably want to flash "SYSTEM", "MODEM", "KERNEL", and "RECOVERY" at a minimum. That said, it would be a *good* idea to use all the files inside the firmware package.
I'd upload packages I've made for my own convenience, but I'm unclear about their legal situation. I think I can get away with PMing links around though. Maybe.
EDIT1: Please post the output from the "Status" box if it fails.

Apologies for not responding sooner. Been busy with work, will try this soon and post results. Thanks

Can't get Heimdall to work. All I get is its not a valid win32 application. I refuse to give up on this, I know it's a software issue so there has to be a way to fix it. ...pulling my hair out though.

Trying to get back to stock - T320

I have been trying to go back to stock on this device, but that's not happening.
My Odin flash:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2171 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet itself, it says Odin: Invalid ext4 image. What can I do?

Aloupha said:
I have been trying to go back to stock on this device, but that's not happening.
...
On the tablet itself, it says Odin: Invalid ext4 image. What can I do?
Click to expand...
Click to collapse
Redownload stock ROM.
Using single or multiple file ROM?
I recommend the latter.
To be downloaded with samfirm_reborn if not found elsewhere.

bmwdroid said:
Redownload stock ROM.
Using single or multiple file ROM?
I recommend the latter.
To be downloaded with samfirm_reborn if not found elsewhere.
Click to expand...
Click to collapse
I have tried several stock from different sources, and it always fail at the same place. I did try the multiple files once and that failed too.

@Aloupha imo Odin 3.14 is to new for this old stock ROM.
Try 3.09 or even older ones.
Somewhere I've read recommendations regarding Odin versions to stock ROM versions.

bmwdroid said:
@Aloupha imo Odin 3.14 is to new for this old stock ROM.
Try 3.09 or even older ones.
Somewhere I've read recommendations regarding Odin versions to stock ROM versions.
Click to expand...
Click to collapse
Oh I will give that a shot and see. I will google for an old version.

I went as low as Odin 3.04... it keeps failing at the same place: Odin: Invalid ext4 image
Do you have a link for samfirm_reborn?

@Aloupha using ecosia search gave me this:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com

And don't forget to check binary or factory mode to get multiple part ROM.

bmwdroid said:
@Aloupha using ecosia search gave me this:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Oh - I did find that link but didn't know I had the right one. I don't know how to use that site.

@Aloupha on the right hand side you see "Releases" below "About".
There is the link to the download site where you find the .zip to be used.
No need to install. Just unpack it and start as admin.
This is the direct link

Ah that makes sense. Not knowing how it work, I was looking to download the firmware directly from the website. That's why I was confused. Thanks for the tip.
Alright, I downloaded the latest firmware from there and tried. I am still getting the same error.
Is there a stock ROM I could flash via TWRP?

Aloupha said:
Ah that makes sense. Not knowing how it work, I was looking to download the firmware directly from the website. That's why I was confused. Thanks for the tip.
Alright, I downloaded the latest firmware from there and tried. I am still getting the same error.
Is there a stock ROM I could flash via TWRP?
Click to expand...
Click to collapse
That will never work as stock ROM includes stock recovery and comes in a different file format.

Perhaps ADB might work but I never tried.
Which Odin right now?
CU in a few hours.

bmwdroid said:
Perhaps ADB might work but I never tried.
Which Odin right now?
Click to expand...
Click to collapse
I have tried Odin 3.04, 06, 07, 09, and 3.14.4, and none worked. I read somewhere that for this to work, I must have the original cable. Since I don't have the original cable, I don't know what to do.
I would give ADB a shot, but I have no clue how to do that.

Aloupha said:
I have tried Odin 3.04, 06, 07, 09, and 3.14.4, and none worked. I read somewhere that for this to work, I must have the original cable. Since I don't have the original cable, I don't know what to do.
I would give ADB a shot, but I have no clue how to do that.
Click to expand...
Click to collapse
Cable doesn't have to be original but of good quality.
Neither do I. I just once checked if tab is recognised and that worked.
Btw does it still work to flash custom ROM?

bmwdroid said:
Cable doesn't have to be original but of good quality.
Neither do I. I just once checked if tab is recognised and that worked.
Btw does it still work to flash custom ROM?
Click to expand...
Click to collapse
I flashed Custom via TWRP if that's what you mean... yes.