Database Users

Important for woot.com [Sprint] Tab Owners

So there may be several of you reading this posting that got your Tab from woot.com. I have been working on getting my hands around this tablet since day 1 and I wanted to stress to each and every one of you that plan on rooting or flashing anything to get yourself a new SD card asap... I found, as well as many others, that the SD card that came from Samsung (16GB) seems to be a problem for the device when it comes to flashing kernels and roms...
I finally was able to get Honeycomb on my device after swapping the 16GB SD card out with a 2GB SD card I had laying around at work. I couldn't get any of the CWM kernels to actually do as it was planned to do until now...
Just wanted to share!

Because I find it important to share what I learned, here are the steps I followed, in as best detail as I can, to obtain root, CwM 3.0, and Spacemoose1's HC Alpha 2.5 build:
First of all a few things to note, some of which is specified above in my previous posting, replace the SD card with another one that’s not from Samsung (as it appears this caused several issues). Odin 1.7 (with .pit) and Heimdall (with 1.1.1 binaries) are your best friends, download them both. Make sure for using Heimdall you have the Microsoft Visual C++ 2010 Redistributable Package (x86). For Odin make sure you have the EA24 .tar, this will be your get out of jail free card if you mess something up (Lord knows I’ve done this like 20 times trying). This simply allows you to reflash your Sprint Tab back to EA24 and you can start over.
Here are the steps I followed to get to where I am now:
-- Took the OTA updates from DJ30 (out of the box at this) to EA24 (eventually started here after using Odin several times) to EB28.
-- Enabled USB debugging (always important to have this one on and, if you’re like me, stay awake so I don’t let the thing fall asleep on me and unknown sources).
-- Obtained root with SuperOneClick (this is very easy to do, literally one click root) and rebooted as specified by SuperOneClick’s direction. I verified root by observing Super User in my apps and downloading terminal emulator, typing “su” in the window and selecting enter to be shown # to verify root.
-- I downloaded the latest and greatest kernel (zImage) and ROM from Spacemoose1’s build thread and placed a copy of the zImage file on my desktop for quick access and the ROM on my SD card of the Tab.
-- Next I unplugged the device from the computer, powered down, and put it in to download mode by holding down the power button and volume down until the shoveling android is shown. I then plugged in my device to the computer and opened up my Heimdall folder I extracted to my desktop and navigated to the Drivers folder and double-clicked the zadig.exe to install the drivers. I selected options and list all devices. From the drop down I selected Samsung USB Composite Device and selected install drivers. If everything goes well it will say drivers are installed successfully.
-- I didn’t leave download mode, I proceeded to flash the zImage file from Heimdall. I opened Heimdall Frontend and, on the left side of the application, selected browse to find the zImage file I placed on my desktop. I ensured the checkbox to the left of the field was checked and selected start. If everything is successful it will flash your kernel and reboot in to recovery and freeze at the Samsung logo. I held down the power button for about 8 seconds until the screen cut off. When the battery icon was shown (with the green color showing amount of charge) I held down the power and volume up button to enter recovery mode. It will attempt to backup and fail, don’t sweat it. Wipe data/factory reset and then wipe cache, then reboot the Tab. It will freeze at the Samsung logo again; just hold power down for about 8 seconds until it turns off. When the battery icon is shown (with the green color showing amount of charge) I held down the power and volume up button to enter recovery mode. This time the device will resume backing up and complete successfully. Once it’s completed, to flash Honeycomb you will need to select install zip from SD card and then select zip from SD and choose the latest ROM that you downloaded and placed on your SD card. It will flash so let it do its thing. It will reboot and eventually load Honeycomb.
MOST IMPORTANTLY JUST READ AND IF YOU'RE NOT SURE ABOUT SOMETHING PM ME AND I'LL SEE IF I CAN HELP!

I also have a sprint refurb woot tab and did not have this issue.
I flashed to hc just fine using superoneclick -> special sprint tab cwm instructions thread (uses heimdall) -> cwm update using sm1's zip file.

Thisrobot said:
I also have a sprint refurb woot tab and did not have this issue.
I flashed to hc just fine using superoneclick -> special sprint tab cwm instructions thread (uses heimdall) -> cwm update using sm1's zip file.
Click to expand...
Click to collapse
Yeah I've seen mixed reviews on how to go about things and many Sprint users, including woot.com Tab owners, experiencing a wide array of issues or none at all. I think documenting all the various issues will give us a better chance of figuring out different approaches that'll be specific to each user.
Just wanted to share another story in detail. Thanks for your input!

I'm one of the one's having no issues at all. I took both updates, rooted the thing and disabled the activation. Have no desire to do anything with it beyond that though. HC just strikes me as half baked. If/when the GB update comes down OTA I'll take it, but I have no plans to flash any ROMS or anything. Only issue I've noticed is that if I don't reboot it every other day or so it develops serious lag. If unaddressed it becomes completely and totally unresponsive. Rebooting it fixes the problem. I may just program Tasker to reboot it at night.

A. Nonymous said:
I'm one of the one's having no issues at all. I took both updates, rooted the thing and disabled the activation. Have no desire to do anything with it beyond that though. HC just strikes me as half baked. If/when the GB update comes down OTA I'll take it, but I have no plans to flash any ROMS or anything. Only issue I've noticed is that if I don't reboot it every other day or so it develops serious lag. If unaddressed it becomes completely and totally unresponsive. Rebooting it fixes the problem. I may just program Tasker to reboot it at night.
Click to expand...
Click to collapse
i noticed a similar slowdown when my tab was on for long periods of time.. If you are using Dolphin HD, install the addon "browse faster." it kills unnecessary processes and makes scrolling/switching tabs more responsive.
OR, you can hold the home key-> hit the task manager button->exit all and/or under the ram tab clear memory.
These work fine for me, and at this point i pretty much never have to reboot because of slow perf.

The original microSD card was unrecognized out of the box, but formatting it on another device worked. Try doing that and putting the card back in.

s44 said:
The original microSD card was unrecognized out of the box, but formatting it on another device worked. Try doing that and putting the card back in.
Click to expand...
Click to collapse
I'll have to give it a shot, even though I just bought a 32GB one for it..

anyone else getting a constant conversion to ext4 when you reboot into CWM? I swapped out the stock sd card for a 1gb card i had laying around, it runs through the conversion, and can read the sd card, but as soon as I flash the HC rom and reboot it just sits at the samsung bootlogo. I power it down, and go back into recovery and it runs the conversion again. The only time it doesn't run the conversion is if i put the stock sd card in, then it just says can't mount /sdcard. this is getting really annoying. I've got an Epic 4g and stuff like this just doesn't happen, so I'm wondering what the heck the issue with the Tab is.
So, figured out anytime I was getting stuck in the ext4 conversion loop for recovery, that I needed to go back and flash the recovery via heimdall again. It seemed every 3rd flash would work. Annoying, but at least now I know.

My card pooped out and they gave me a $20 credit. Time for a class 10 16gb card. Maybe the dead one will come back to life!
- Z

I bought a refurbished Sprint Galaxy Tab from meritline.com. Probably of similar heritage to the one Woot was selling.
So far my 16GB SDCARD has worked without any problem. I have (just for the heck of it) ordered a 32GB Class 10 card to use in the Galaxy Tab.
Am waiting for Spacemoose1 to release a Honeycomb beta version. Will probably dive into HC at that point.
And if someone figures out how to get Netflix flying on the Galaxy Tab I'd be interested to hear all about it.

Another question -
Since my Sprint Galaxy Tab does NOT have any active data plan, will it still acquire OTA updates? Mostly I'm curious about the upcoming, promised Gingerbread update from Samsung.
Or will I have to manually install it. Since KIES does not function on these CDMA tablets it leaves me wondering just how this update will find its way to my Galaxy Tab.

I also don't have a data plan with sprint, and I've received OTA updates (possibly pulled down via wifi) so hopefully if we do get lucky enough to get an official GB update, it'll come OTA even without a data plan..

pvtjoker42 said:
I also don't have a data plan with sprint, and I've received OTA updates (possibly pulled down via wifi) so hopefully if we do get lucky enough to get an official GB update, it'll come OTA even without a data plan..
Click to expand...
Click to collapse
My Samsung Fascinate is on a data plan with Verizon. When an OTA download is available and I request the update via the phone settings, it ALWAYS cautions that it is about to disable the WiFi in order to access the OTA update.
I do not know if the same is true of Sprint as I've never had an activated Sprint phone . Seriously hope not as it might make it less than straight forward to acquire the OTA updates such as Gingerbread.
Time will tell.

warranty on a refurbished galaxy tab
Hawk521,
I am thinking of buying the one from meritline too. I am concerned as to who did the refurbishing. Was it Samsung? How come there is only a 90 day warranty as opposed to a year for a new one? Is it worth spending more for the full warranty?

pvtjoker42 said:
anyone else getting a constant conversion to ext4 when you reboot into CWM? I swapped out the stock sd card for a 1gb card i had laying around, it runs through the conversion, and can read the sd card, but as soon as I flash the HC rom and reboot it just sits at the samsung bootlogo. I power it down, and go back into recovery and it runs the conversion again. The only time it doesn't run the conversion is if i put the stock sd card in, then it just says can't mount /sdcard. this is getting really annoying. I've got an Epic 4g and stuff like this just doesn't happen, so I'm wondering what the heck the issue with the Tab is.
So, figured out anytime I was getting stuck in the ext4 conversion loop for recovery, that I needed to go back and flash the recovery via heimdall again. It seemed every 3rd flash would work. Annoying, but at least now I know.
Click to expand...
Click to collapse
I got around this by formatting, partitioning and converting to ext4 using my Evo4G.

alans75 said:
Hawk521,
I am thinking of buying the one from meritline too. I am concerned as to who did the refurbishing. Was it Samsung? How come there is only a 90 day warranty as opposed to a year for a new one? Is it worth spending more for the full warranty?
Click to expand...
Click to collapse
I don't know who did the refurbishing. On items like this that have only been on the market for 7 months or so, most 'refurbs' are likely simple product returns from buyers who were not happy for one reason or another. I've bought lots of refurb items over the years and have yet to have any regrets.
FWIW, mine came in a brand new looking oem box, the power supply and cables were still in the oem packaging and all documentation was pristine.
If it suits your needs go for it. Sure beats spending $350+ bucks on one. I'm not using any Sprint 3G data plan - just treating this as a WiFi only tab.
Also, just today it leaked out that Sprint will be providing an OTA update to Gingerbread starting on July 5th, 2011.
http://www.engadget.com/2011/06/30/sprint-updating-the-samsung-galaxy-tab-with-gingerbread-on-july/

pvtjoker42 said:
anyone else getting a constant conversion to ext4 when you reboot into CWM?
Click to expand...
Click to collapse
After it fails the first time (and while you're still in the CWM utility ROM go and clear the two cache settings prior to restarting into CWM rom again. Clearing the caches (one is under the advance setting) will clean things up so that upon the next bootup CWM will properly convert to ext4.
At least that is what I've seen several times now.
Good luck with it.

Gingerbread for Sprint on July 5th?
Has anyone had any luck with the July 5th Gingerbread upgrade that Google and Sprint have indicated would begin downloading on July 5th?
I realize they may roll the update out over several days, but so far my attempts to prod the update manually have met with no results.
If anyone has better luck please post it here. Also note if your Galaxy Tab has a current Sprint data plan, or if it is like mine, a refurb that has no current contract for data.
Watching and waiting...

Hawk521 said:
Has anyone had any luck with the July 5th Gingerbread upgrade that Google and Sprint have indicated would begin downloading on July 5th?
I realize they may roll the update out over several days, but so far my attempts to prod the update manually have met with no results.
If anyone has better luck please post it here. Also note if your Galaxy Tab has a current Sprint data plan, or if it is like mine, a refurb that has no current contract for data.
Watching and waiting...
Click to expand...
Click to collapse
My non-activated sprint galaxy tab just only show me "Unknown Error", when I try Setting->About My Galaxy Tab->System Updates->Update Firmware.

Xoom: Update Canadian device to ICS through US Image

Impatiently waiting for ICS, I rigourously went through the process this evening of putting the US image on my Xoom in hopes of the upgrade path being opened up to upgrade to ICS (yes, I know various music services still won't work in Canada). I'm an expert at Linux, an experienced Android developer, and had the SDK already installed.
No problems going through the whole fastboot flash proces that is well documented in various postings here (I am working from Ubuntu 11.10 from a root account).
Side note: the USB cable does seem to need to be plugged into a rear USB port. It was a little unreliable from the front ports. Try this if you get the pesky error "Failed to process command error 0x120003".
After doing the oem lock step, the device fails to load the kernel. At this point I thought I had bricked the device as it wasn't clear how to get it back into the fastboot mode. Pressing PWR+Vol Down does work after somewhat of a pause.
Unlocking the device will allow the US 3.0.1 image to boot, however the 3.1 OTA updates downloads at this point but does not work - it gets you to the evil "green android triangle exclamation point" image. Dead end.
At this point you really have to download the Canadian 3.0 image and start back at square one and go back through the OTA upgrade path. I did notice along the way that the Canadian look/feel is slightly different from the US one and there are some Motorola add-ons. Why???
That's three hours of my life I'm not getting back. Wanted to save some other people the trouble: if someone were weak in their computer skills they could easily get stuck with a bricked device.
I'd be a happier customer if Motorola could let us know when the Canadian ICS update will be ready.
Hope this helps somebody.

I did this no problem and I just rooted and added a custom rom .... I'm 14. Not saying its as easy as slicing bread or whatever but still its extensively easy.. you also don't even need to leave it unlocked you can relock it if you want.

[Q] Problems rooting updated S4

Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.

You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent

ifly4vamerica said:
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
Click to expand...
Click to collapse
No my S4 was in camera mode. There are 2 options when I plug my phone in via USB to the PC, either camera mode or media device mode, PTP and MTP respectively. This is how it was set up before I turned the phone off to go into download mode, didn't think it made a difference, but I wanted to give as much info as possible. The phone went through all the downloading stuff on-screen with the red pirate android guy and everything while Odin was downloading to the phone, and Odin also said Added in the message box so I figure Odin recognized the device was present. I'll check out that thread though, thank you:good: I'll be back here if it doesn't rectify the situation.

I see my first problem, stupid tutorial I used the first time said to put Odin in Repartition and F-Reboot. QBKing says only Autoreboot. Man I hate crappily done tutorials.
Just also noticed he mentions the yellow box and com/port number are vital to the success of the root, something I overlooked all 3 times I tried it.

Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.

pumpdatbass420 said:
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
Click to expand...
Click to collapse
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you

saj070 said:
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
Click to expand...
Click to collapse
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?

pumpdatbass420 said:
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
Click to expand...
Click to collapse
step 2 is open dialer on the phone - how else you going to press ##3424#
i thought that was a given sorry

It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.

pumpdatbass420 said:
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
Click to expand...
Click to collapse
no problem better be safe than sorry ')
let us know how it went.

It's aliiiiiiive
Ok so oddly enough, after I performed steps 1 & 2, when I rebooted my phone I notice SuperSU was in my apps list. So for $#*^$ and giggles I downloaded Root checker to test it out and sure enough it says device is rooted. Go figure.
Thanks so much for your help guys, my girlfriend was starting to worry about me out here smashing keys and grunting like an animal trying to get this to work. :highfive:

pumpdatbass420 said:
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
Click to expand...
Click to collapse
try doomlord easy root

Thanks for the tip but I already got it rooted. Just took a few more steps than I thought due to some overlooked details with the initial install.

New problem!
Trying to get QBKings Native Hotspot mod to work and it wont let me transfer services.odex to the system folder but services.jar is transferring fine? Any ideas? I'm baffled here yet again. Tried 3 different root browsers but JUST services.odex wont transfer!!!!!

Sorry for joining late, but how are you transferring the file? ADB, SD?

Need root without computer, bootloader unlocked...

I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...

If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.

Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...

Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck

Just a warning

I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.

You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk

This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.

RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.

download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.

RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.

First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.

LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.

RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...

Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I

Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.

LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.

AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89

scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2