Database Info

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!

Still having Tab2 woes

I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? I wish I had seen this before I read "that it was almost impossible to brick the tab 2"
Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now

gbswales said:
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
Click to expand...
Click to collapse
Have you tried a factory reset from recovery? If you've restored the stock ROM, then all you need to do is the factory reset to get things working again. Don't repartition unless you really need to.
gbswales said:
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
Click to expand...
Click to collapse
I can't see any reason you should spend that kind of money given how easy the CF-AutoRoot is. In fact, that product looks very shady to me. "Root Any Android Device"? Well, there's lots of devices out there that nobody's been able to root, or devices that take a lot of work. I can't believe there's a single app that'll work across every Android device with a single click.

Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot

CWM ?
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
Well I followed one of the posted routes on this forum, downloading from a list of recommended files for each version, and it mentioned nothing about CWM which I know nothing about. I have to say that everyone's definition of "easy" on here - I find complicated and difficult - I know my way around windows but android seems much more complex. The only reason I wanted to have root in the first place was to be able to make a complete image back up that would make it easy to restore my device without having to re-download all my software and set up. I do it with windows all the time. To me "easy" is, download and install something - click go - done! Even getting the device to go into download mode in the first place is a very hit and miss affair (as others say on here too) clearly Samsung don't want you to do this.
The other problem is that while the tablet is in this state it wont turn off, just reboots itself when you do and the screen stays on - so unless you leave it plugged in 24/7 - I start each time with a flat battery that I have to recharge before I can try something else

This is the route I followed
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
I got this through earlier posts - the only thing I didn't do was to go into recovery and reset in step 2 because this simply wasn't possible - the device was stuck on the error message and no amount of button pressing did anything other than restart to the same screen. By this stage I couldn't even go back to check what version of android I was running - it would have been the latest jelly bean distributed to UK.
I also didn't check re-partition as in 6. because there was no pit file in the download
E. Restore to stock
THIS WILL WIPE YOUR DATA!
4.0.3 for p5100: https://hotfile.com/dl/155804946/76b...XALD9.rar.html
4.0.3 for p5110: http://www.hotfile.com/dl/159635395/...3_PEO.zip.html
4.0.4 for p5100: http://www.hotfile.com/dl/165065733/...1_SER.zip.html
4.0.4 for p5113: http://www.hotfile.com/dl/164415704/...5_XAR.zip.html
4.0.? for p5113: http://69.46.67.99/GT-P3113_XAR_1_20...ldcgx9tzmx.zip
4.0.4 for p3100: http://samsung-updates.com/fw/Samsun...3kdo3qe503.zip (PIT files: 16Gb p3100, 8GB p3100
Note: for more language options for stock ROM's for the tab 10, go here.
1. Unzip the downloaded ROM. If there is a file ending in .pit, skip to step 3
2. Reboot into recovery and select wipe data/factory reset.
3. Reboot into Download Mode.
4. Unzip/unrar the stock firmware
5. click PDA and find the stock file (PDA/PLATFORM file, the largest one).
6. Click PIT and open the .pit file you downloaded if one was included with your ROM. Check Re-Partition in ODIN
7. OPTIONAL: if you want to flash the bootloader and/or csc, you can select them as well. If you don't know what that means, you don't need to do it.
8. Click Start.
9. Enjoy!

Help please - this is where I am at the moment - some SIMPLE help needed please
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.

gbswales said:
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
Click to expand...
Click to collapse
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.

Thanks K1MU for this information which at least looks clear - the only problem I have is when I put in the model etc when I get to country it offers me only 3 choices
UK (BTU) GB (O2) or GB (vodafaone)
My phone was purchased from Amazon and is unlocked so I am worried if these might lock me to a carrier which I wouldn't want
I wonder if BTU is the unlocked one as it doesn't sound like any provider I know - but I am not sure
will post on their forum as well

I think I am getting more and more muddled by the minute (sign of old age I fear) I realise now that I have a p5110 - wifi only and not p5100 3g and wifi.
This means in all probablilty I downloaded the correct rom in the first place. As I had not done the factory reset afterwards so tried that - it appeared to work ok but when I restarted it just played the samsung tune and moving image - then went to "Samsung" and stuck there as it was before.
I am downloading the p5110 wifi only rom from Sam's site - awful download programme they use which doesn't accept paypal even to sign up for faster downloading - I will then try following exactly what you have suggested and keep my fingers crossed

thank you
k1mu said:
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Click to expand...
Click to collapse
Although I thought it had got nowhere after wipe restore - when I turned it back the next day I arrived at the start up guide - admitedly it was 4.0.3 and in Portugese but after exploring settings and working out what to click i got it back to uk english - it has now connected to kies ok and is currently downloading the latest firmware - thanks partcularly to the last poster and to all others who helped - I will go through and thank you others too,
Point is now - once I have jelly bean can I get root access easily -without installing another custom rom - ahh well tomorrows problem

I need help rooting my New Tab 7.7 i815 guys!

I have searched all over the web and this forum and after literally days of searching all I have found seem to be from late 2011. And none of the several methods will to root my Galaxy Tab 7.7 i815 Verizon LTE tablet. My question is, is there a current way to root my tablet? I really want to root and custom rom my tablet, but I am ready to pull my hair out. I have rooted my Galaxy S4 and flashed a custom rom and it was so easy, and is just so much better. I woulsd love to flash a Jelly Bean rom on this tablet, thats my goal. Any help would be hugely appreciated. Thanks

ddrumbum said:
I have searched all over the web and this forum and after literally days of searching all I have found seem to be from late 2011. And none of the several methods will to root my Galaxy Tab 7.7 i815 Verizon LTE tablet. My question is, is there a current way to root my tablet? I really want to root and custom rom my tablet, but I am ready to pull my hair out. I have rooted my Galaxy S4 and flashed a custom rom and it was so easy, and is just so much better. I woulsd love to flash a Jelly Bean rom on this tablet, thats my goal. Any help would be hugely appreciated. Thanks
Click to expand...
Click to collapse
You don't need to root to install a custom ROM. You need to flash a recovery, and then use that to flash the ROM. I'm not sure if Verizon added more difficulties to install a recovery, though; my P6800 was as easy as it gets to go from Honeycomb to anything else.
Recoveries: http://forum.xda-developers.com/showthread.php?t=2352967
JB ROMs: http://forum.xda-developers.com/showthread.php?t=2139766
Good luck!

Steve_max said:
You don't need to root to install a custom ROM. You need to flash a recovery, and then use that to flash the ROM. I'm not sure if Verizon added more difficulties to install a recovery, though; my P6800 was as easy as it gets to go from Honeycomb to anything else.
Recoveries: http://forum.xda-developers.com/showthread.php?t=2352967
JB ROMs: http://forum.xda-developers.com/showthread.php?t=2139766
Good luck!
Click to expand...
Click to collapse
Thanks Steve! I feel like an idiot looking all over for a root and not a flash. Ok could you tell the steps to flash this please. Please forgive my noobness, and thank you so much for your reply! I think I have an idea how to do it, but I just want to be certain.

I need the same thing. Let me know how it works out

ddrumbum said:
Thanks Steve! I feel like an idiot looking all over for a root and not a flash. Ok could you tell the steps to flash this please. Please forgive my noobness, and thank you so much for your reply! I think I have an idea how to do it, but I just want to be certain.
Click to expand...
Click to collapse
taiwwa said:
I need the same thing. Let me know how it works out
Click to expand...
Click to collapse
I'd rather let someone who actually owns an i815 give you exact instructions, but the general idea for Samsung devices is:
- Get Odin on your PC, for example, from here
- Reboot your device to download mode (power off, then power it on while holding volume down or volume down + home)
- open Odin
- Put the recovery .tar (or .tar.md5) file on "PDA", DON'T CHANGE ANYTHING ELSE, and click "start". The file will flash, and then the device will reboot
- To enter the recovery, power on while holding power+vol. up
- Make a backup
- Factory reset
- Install the ROM .zip
I can't tell you if this works on the Verizon version, though; or if there is anything else involved. I have an international P6800, where this works fine. Maybe someone who has the same version can help?

Steve_max said:
I'd rather let someone who actually owns an i815 give you exact instructions, but the general idea for Samsung devices is:
- Get Odin on your PC, for example, from here
- Reboot your device to download mode (power off, then power it on while holding volume down or volume down + home)
- open Odin
- Put the recovery .tar (or .tar.md5) file on "PDA", DON'T CHANGE ANYTHING ELSE, and click "start". The file will flash, and then the device will reboot
- To enter the recovery, power on while holding power+vol. up
- Make a backup
- Factory reset
- Install the ROM .zip
I can't tell you if this works on the Verizon version, though; or if there is anything else involved. I have an international P6800, where this works fine. Maybe someone who has the same version can help?
Click to expand...
Click to collapse
okay, well,
First of all, I couldn't find the backup option so I just wiped the device.
Secondly, I have one of the CWM 10.1 zips on my sdcard. I keep on getting the error "failed to verify the whole file structure."
edit: okay, this is the real problem. I can't get the CWM or the TWRP recovery on the samsung tab 7.7 via Odin. That is the real problem.

Okay, I figured it out. Basically, the hiccups come from two things: have to make sure USB debugging is selected in the developer options in the settings.
Secondly, it appears that CWM needs to not have the USB plugged in when you want to activate its recovery mode.
Now, all I need to do is figure out how to install the play store.
And...I"m afraid that from now on, system updates means that the entire device gets wiped?
CM10.1 JB is sooo much better than the lousy Samsung touchwiz or whatever junk that they came up with.

It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.

taiwwa said:
It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.
Click to expand...
Click to collapse
FANTASTIC! THANK YOU SO MUCH! One last question. You said "Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd" So which ones did you use? I just don't want to screw anything up. Thanks again.

HELP!!
taiwwa said:
It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.
Click to expand...
Click to collapse
ddrumbum said:
FANTASTIC! THANK YOU SO MUCH! One last question. You said "Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd" So which ones did you use? I just don't want to screw anything up. Thanks again.
Click to expand...
Click to collapse
OK I followed your steps flawlessly, and my screen will not go past the paranoidandroid 3+ boot screen. Please help me I'm freaking out

Try framaroot. Install the app, usb debug on and root.
Now you can install recovery with a lot of apps.
Habby rooting

[Q] Help with KitKat + CWM 6.0.4.6

Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!

SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.

LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.

Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime

I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!

I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/

jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.

It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!

kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..

amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.

still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​

shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.

voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)

jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need

Need help with Samsung Tab 7.7 (SCH-I815LSV)

I'll give you the whole story so bear with me. First off, I'm very new to the Android OS and tinkering with phones and tabs. I'm a computer network administrator and pc mechanic. I'm mainly a hardware guy though, no programming experience at all. But I'm not afraid to jump right into the inner workings though, especially if it's already broken.
And that's probably why I find myself in this position today with this device.
I recently bought this Tab 7.7 to use as a display for my new drone. When it arrived I tried to download the flight control app and it refused to install. No error messages, it just did not install. In looking, the unit was on Honeycomb 3.0. My guess was it was WAY behind in upgrades so off I went to make it bigger and better. I downloaded a zip file for Lollipop 5.1 onto my SD card and was able to load that. Upon reboot I had a screen and an OS. I went into settings and saw where it had upgraded. Success, right? Well, then I went into Wi-Fi settings to add my network. The keyboard would not come up on screen. So I did a bit more research and tripped over the fact that I needed to also load a GAPPS file to add the apps and drivers back. THAT is when I went down the rabbit hole.
The install did not go well and I somehow wound up with no OS at all. Probably after thinking I was following the correct process of resetting and clearing caches before installing the new files. Then this 3 day journey of learning began. I have downloaded Odin, Notepad++ to edit files, Minimal ADB and Fastboot, Samsung KIES and all manners of ROM builds and GAPP files. As of this moment I have absolutely no OS on the unit. Upon turn on it goes directly into the CWM Recovery v6.0.4.5 screen. I am able to boot it to the download screen and Odin can SEE the unit. But I can't get any further with that program other than seeing the unit listed as detected. I'm not able to get anywhere with KIES. No detection or anything.
Now I'm admitting I messed this unit up. I'm not blaming any written procedure or ROM developer. I'm not stupid but evidently don't know all I NEED to know about this process. So I'm here asking for guidance. I really would like to revive this unit and get it back to where I can use it as my monitor as originally planned. But one step at a time. Please give me the correct steps to do to get an OS reloaded and revive this unit.
I'm thinking that my best bet would be to use a TWRP image file to rebuild it. But I need the step by step process for that to make sure I do it correctly.
MANY thanks for this board and the help AOT!!!
Dave

Being the impatient type as well as a DIY'er, I pressed on with trying to revive it myself. I downloaded TWRP as a zip file and added it to the SD card. Booted and installed from the zip file. Screen said it loaded successfully. I rebooted and tried going into recovery (holding power and volume up) expecting it to go into the TWRP console. Instead it went into the regular CWM Recovery screen. Oh well, another frustrating dead end for me. I'll just set it aside until I get some good instructions from someone that knows what they're doing. Best I do that rather than brick it. I can at least access the recovery screen. Odin sees the unit but I cannot find the right file to load from there.

Okay, I'm truly stopping now. Another dead end. I was able to find a couple of files for restore using Odin. Loaded one and now I boot into Android system recovery <3a> instead of the CWM Recovery screen as before. I tried loading a recovery image from a zip file and it failed signature. That seemed to be telling me the tab is now not rooted. So I downloaded SuperSU to the SD card and tried to load it. No joy, it fails signature too.
Arrrggghhhh.........

Can't even shut it down.

Told you I'm impatient. Now have used Odin and installed TWRP 3.0.2-0. Going slowly now. Taking it one step at a time. This is the first positive step I've had so far in 3 days.
:silly:

Baby steps. LOL
Used TWRP to flash SuperSU. Now the unit is rooted and rebooted to TWRP. I still have no OS on there as of yet. I'm guessing my next step is finding a good stable ROM file and use TWRP to flash onto the tab.

Downloaded OmniROM Marshmallow 6.0.1 (https://androidfilehost.com/?w=file...69dc16313bf0332c8794621c6c7f505edf855e0d499d8) and the Open GApps ARM 6.0 stock file (http://opengapps.org/).
Will try to flash those through TWRP and hope for the best.

Joy...at last. The downloaded OMNI 6.0.1 worked when loaded using TWRP. The GApp file failed. Will try another one to see if it works.
https://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Booted to TWRP and was going to install the GApps file. I had left OMNI 6.0.1 on the card too and by mistake selected it. Dooohhh......
I'm an accident waiting for a place to happen. LOL
So, after REloading Android 6.0 I proceeded to load the gapps base file. Reboot and all appears to be going smooth. Apps updating and such. After about 2 minutes I get a message onscreen that unfortunately setup wizard has stopped. Hit okay but the message persists to pop up.
So.....
I guess I'll take a short break then do a wipe and reload of the OMNI and the working gap file and see what happens. At least I got to see it actually boot and let me get into setup. I went to add my Wi-Fi network, added the credentials but it never connected. Something else to look into.
More fun ahead....but at least I'm moving forward now.

A happy camper. Because I was able to revive this tab and because I had the patience to figure it out myself. And my wife swears I have no patience.
LOL
So...the key was downloading Odin and the Samsung drivers on my laptop.
Then download the TWRP.tar file to the laptop.
Boot the tab into download mode by holding power and volume down button. Select yes to continue.
Connect the tab to the laptop with the USB cable. See that Odin can communicate with the tab.
Select AP and find the TWRP file location and start. After it finished, rebooted and since there was no OS installed, TWRP recovery opened.
The next thing was download SuperSU file and drop it onto the SD card. You CAN go ahead and find the correct ROM you want and download the file as well as the GApp file. Drop all 3 onto the SD card.
Then insert it into the tab and select Install. Just be very observant WHICH file you load in what order.
You will need to install the SuperSU, reboot and then install the OS ROM followed by the GApp file.
Select SD card and the SuperSU file. Wait for it to complete then reboot.
After loading SuperSU and reboot, you need to get back into TWRP Recovery program by rebooting while holding power and volume up. This time when you select Install, pick the ROM file first then pick additional files and select the GApp. This way TWRP will first install the OS from the ROM file and immediately load the apps file. Then reboot and you are done!!!
And it took 3 days of round about to figure this out.
LOL
I just downloaded my flight control app and I'm off and running with Marshmallow.
Hope this helps at least one person that is new to this whole process as I was!!!
Dave