[Trifecta] Jelly Bean Root - Motorola Droid Bionic

****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.

I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.

Related

[Q]How to activate G1 through wifi?

Upon reading the title you probably entered ready to flame me for not using the search button. The reality is though, that is just one of my many problems I'm having. I'll start from the beginning, give you the whole rundown and hopefully you can help, because if I can't figure this out soon I'm going to start smashing things, my G1 being first on the list.
A couple of days ago i was just surfing around, heard about custom ROMS, rooting, etc. so I started my journey. Thinking this would just take an afternoon, at the max, was a mistake on my part. I started here:
[ROM]TheOfficial TMO (US/EU) & HTC ADP - CRC1- Rooted [8/17/09]- v1.5.2-SecurityPatch
Looking at the prerequisites, I realized I lacked both the requirements so I followed that threads link to here:
Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
I was able to complete up to step 7, but 8 posed a problem.
When trying to sync my google account to the phone it gave that old message we all know and love from when the G1's were just released. The one where it tells you: "There is a problem communicating with the Google servers. - This could be a temporary problem or your SIM card may not be provisioned for data services. If it continues, call Customer Care."
At first, I thought maybe it was because I had horrible service in my house, ranging anywhere from 0-2 bars. Thinking I could easily fix the problem by walking up the road to get 4 bars, that's what I did. Still having trouble communicating with the servers. It's obviously not server overload like they tried to say at launch and it can't be I don't have data services because I've been paying and using them for about 9 months now. So I set off to the internet for a fix. I came across this:
[How To] Activation over Wifi
Reading the first sentence, it told me to set up ADB. So I went here:
Setting up ADB
But, I obviously couldn't complete the steps listed because I can't set my phone to debugging mode with out it being activated. So I went back to the Wifi act. page and scrolled down to find this:
[How To] Activation over Wifi (12th Post)
Following the first step, I typed <enter>reboot<enter> and nothing happened.
This, obviously, confused me very much. Because, did I not just wipe my whole phone and install rc29?
But I disregarded it, putting it to the side as a fluke and hoping the rest would work anyway, because at this point I just wanted things to start working.
I went to step 2, but once again I can't do that because I don't have access to the phone settings.
But I just continued.
Upon trying to complete step 5, I was just pissed... This seems like a never ending road. Of course, my phone had to be wrong and show up as a USB mass storage device. So I followed the steps, but I don't understand part D in step 5 because it only gives me one choice on the list which is USB mass storage device. After this I started trying everything, uninstalling that driver, turning of PnP, just about everything I could think of.
If someone could just help me, even a little, I would be so very happy.
If you need any info at all just, pictures, build info, w/e I/'ll have it to you as soon as I see your message. If you don't understand something I said, ask right away and I'll answer. Thank you so much in advance lol
Mind you, I've tried all these guides a couple times over, I've tried different guides and I've installed rc29 3 times now. Still no luck
I'm confused....
I have a few questions before we start you on the journey to getting you rooted.
Firstly, am I understanding things correctly when I assume that you have already flashed DREAIMG.nbh (RC29) onto your phone and can't get past the setup screen?
Secondly, you say that you have data service, but then say that you didn't have enough "bars" so you headed up the street for more "bars". Are you sure you have data service because the bars on the phone have to do with cell reception and have nothing to do with data service.....
Thirdly, are you on 3G or EDGE in your area?
If you do indeed have a data plan for sure, then other than a crappy 3G or EDGE signal, there really shouldn't be a reason for the error message your getting other than google's servers might actually be experiencing difficulty. No way to know for sure.
If/when you are able to get past the login screen to root, go to this link
http://forum.xda-developers.com/showthread.php?t=548924
instead of Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
its recently updated, and easier to follow.
I have bad service...
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
KingTasty said:
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
Click to expand...
Click to collapse
If you cannot get adb working properly, then you cannot use JF's method to bypass the signin screen therefore you just have to wait until you can get to a better service area.
Your two choices are: bypass the signin screen or sign in over the network. You can't sign in over the network as previously stated by you, and you cannot bypass the signin screen because you can't get adb working. There is no way to setup wifi within android if you are stuck at the signin screen
but wait?
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
KingTasty said:
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
Click to expand...
Click to collapse
There are plenty of guides on how to get adb working... its just so happens that you reported that you can't figure it out. If you can't figure it out and get it working, then you can't use the sign in screen work around as outlined in JF's post.
The very first step in JF's work around is
You have to connect to your phone with adb shell and get root access, and then type the following command:
Click to expand...
Click to collapse
Since you can't do that, you can't do the work around. Try reading up more on adb and see if you can get it working.
Couple questions
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
OMG help me too i have the same problem !!!
KingTasty said:
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
Click to expand...
Click to collapse
I know for a fact there that I saw some terminal command not too long ago to be able to activate usb debugging from the command line. I can't for the life of me remember where I saw it, but if you can be patient, I may be able to find it eventually.
florevil said:
OMG help me too i have the same problem !!!
Click to expand...
Click to collapse
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
KingTasty said:
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
Click to expand...
Click to collapse
RC29 has the hidden shell also which is what allows the telnetd command to be entered to start the rooting process. It sounds like when you enter the reboot command at the welcome screen you should be getting a reboot because you said you installed RC29. It also sounds like your doing the commands in the correct spot but just to recap, you should be at the "touch the android to begin" screen, once there, just slide out the keyboard, hit enter, type reboot, hit enter again and the phone should reboot.
What happens if you keep trying to follow JF's guide even though you can't get the reboot to work? Have you made any promising progress with steps after the A few tips and tricks section?
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
KingTasty said:
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
Click to expand...
Click to collapse
Glad to hear it and yes, your right, nothing that you can see will happen. Essentially what it is doing is executing the command behind the scenes same as would happen if you were to hit the check box next to usb debugging if you were able to.
The way you will see if it worked is you should be able to open up a command prompt assuming your a windows user and type:
Code:
adb devices
You should see a device listed something like HT.........
Lemme know if you have anymore problems
Still nothing.
I tried but I don't think it worked, but it may have. The problem could be my drivers so I followed this.
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Click to expand...
Click to collapse
I did that but every time I plug my g1 back one it makes a new one, calling it USB Mass Storage Device. I keep deleting it but it keeps coming back every time.
Here's what I got in cmd.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tyler>cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools>adb devices
List of devices attached
C:\android-sdk-windows-1.5_r3\tools>adb shell
error: device not found
C:\android-sdk-windows-1.5_r3\tools>
I'm not really sure what to do now... I guess I keep trying to see if it'll work. Meanwhile, what do you think?
King,
PM me your contact info and I'll try to troubleshoot this with you. I did it the old fashion way without any programs and I think I remember my steps so I just have to walk through it again.
You could also try this adb tutorial, thats the one I used and would use if I were to walk you through it.
http://forum.xda-developers.com/showthread.php?t=502010
Alright yeh, sounds good.
Gimme like 20 min, I'm gonna go grab something to eat quick.
Take a look here though, I uploaded what re appears every time I plug in my g1. Something must have been turned on or changed be cause now 3 new drivers appear every time instead of just one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But still no luck in cmd, so something is still wrong...
Hi! I have the same problem too. There're a lot of tutors online but they are just copy and paste from each others. I did pass by the first time via wifi when I root my G1 but cann't the second time rooting my girlfriend's.
The USB driver that window or HTC using before works on vista and only see the device as ADB composite deivce, but not anymore, Windows now recognized the devices as ADB composite device AND mass storage. I don't know about XP. and don't know what to do about it
I think that's why I can not enable ADB on G1 by typing "setprop....enable 1"
Anybody help? Offering your Tmo SIM card for 5 mins? I am at Dallas. Txt [email protected] #469-759-9897 Really need it PLZ
I guess this is obvious but I just want to clarify: Everytime you flash the rom you need to re-activate the phone? Or is activation only a one time requirement?
I just purchased a used, tmobile g1 (from the US) and am hoping to root it and flash SuperD's wrong as soon as I get it. However, the problem is I obviously don't have a Tmobile SIM and I don't have a data connection on my local sim card.
Do I have to go through these ADB steps to activate the phone? Thanks!

[Q] I want to make sure I have this right

Sooooo I came up on a T-Mobile G1 from a buddy of mine. A little beat up but after 3 and a half years with a t-mo wing it's about time to upgrade my old phone for a not so old phone. Went through the effort and went through my buddy @ likenewcells.com to get the thing unlocked rather quickly I might add.
My scenario, I don't have a data plan... I have scoured the threads about how to register your G1 without a SIM or data endlessly only to be stuck at getting the adb drivers installed. One key thing I have done so far is downgrade myself to RC29 so I can confirm <enter> reboot <enter> works Yet for the life of me I have tried yelling at it, insulting it, even sending it death threats... NOTHING! hehe
Upon further reading it's mentioned that I need to root the thing first to get adb working, is that correct? I have heard the legends of a rooted phone and the fortune it brings. Unfortunately if I am unable to get past the registration screen then what am I to do? Given that all of the guides say you need to do some things on the phone. Mess with this setting, download something from a site using the browser, whisper sweet nothings in it's ear. I've read many guides in the past week on how to get adb working. One similarity is "you need root access" in them all casual like. Not bad mouthing any of the guides and what not hehe.
I appreciate any information anyone is willing to share with me regarding how to get adb working and / or rooting given my situation. I waited a while to make a post here after carefully reading and scouring the many tutorials for a solution to either. My t-mo wing is falling apart literally and I am done with it.
There is one thing that did help me think maybe just maybe is I was able to enable adb by typing <enter>setprop persist.service.adb.enable 1<enter> Unfortunately I still couldn't get the drivers installed.
Now a healthy question I feel would be is there a similar command I can type at the no sim card screen to get into my wifi settings?
Once again I thank everyone here for any info they're down to share with me.
Winmo - I'm quite familliar, Android I am a complete N00b

[Q] Spoof Mac Address

been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
Edit*
Temporary Fix:
1) Go to wireless & network settings
2) Disconnect and forget ALL previous SSID's that you connected to before
3) download a terminal emulator from the market
4) type the following, make sure you hit enter after every line
Code:
su
busybox ip link set eth0 address XX:XX:XX:XX:XX
Where XX:XX:XX:XX:XX is, make you have to put the MAC address you want there.
to confirm if it worked type:
Code:
busybox ip link show
it should show the new MAC address. Go connect to your network as normal.
NOTE:
If you go to the status option in the settings, you will see that the MAC Address DID NOT CHANGE. This is normal. It wont show the new MAC Address; at least it didnt for me.
One thing to keep in mind, sometimes you cant just put in an hexadecimal combination and expect it to work. It didnt work for me. So what I did is I connected to the school's network from my vibrant making sure I could surf the internet. then i disconnected and copied its MAC address to my tab. when i tried putting in my own custom MAC address, it didnt work. I could connect but packets wouldnt be sent.
Unfortunately when I reboot, my settings are not saved and I have to repeat the procedure. Simplest fix is to just download gscript lite from the market and put in the command I wrote above and whenever i restart my tab run the script quickly. If someone knows of a permanent fix, please let me know so I can update this.
feels good to finally be able to connect after 3 months.
I wrote a quick app that will do this - but i hardcoded the script for something else. I will modify it tomorrow so you can customize the script it runs and put it up here tomorrow or sunday if i get the time.
I would sincerely appreciate that!
Sent from my GT-P1000 using Tapatalk
ayman07 said:
One thing to keep in mind, sometimes you cant just put in an alphanumeric combination and expect it to work.
Click to expand...
Click to collapse
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
AlexTheStampede said:
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Fixed
Sent from my GT-P1000 using Tapatalk
Ok here is the boot script loader.
I didn't spend any time on the interface or layout for you:
Obviously requires root to run
you don't need to start script with "su"-everything runs as su
enter the script in the edit box, click test to test it, click save to save it. It will run whatever has last been saved every boot.
Do NOT move to SD card or it will not pick up the BOOT_COMPLETED intent
i haven't tested if it runs before the SD card is fully mounted: so don't get carried away with your scripts. I suppose I could add options to run only after SD card is mounted but... i probably don't have time
Since this runs as root, do stupid things in your script things at your own risk. I'm not responsible in anyway.
the output from testing or from the boot log is:
stdOut
..some stdOut text
stdErr
..some stdErr text
where stdOut text is the results of your commands (you can see testing with a simple script containing just "ls" without the quotes)
and stdErr is any errors that occurred while running the script (you can see testing with a simple script containing "aasdf" without the quotes
click the "Thanks" button if you use this and it works
i really appreciate this. unfortunately i wont be able to try it out till monday when im at school. ill update it then.
thanks a lot of the script loader. it seems to do its job. but it seems my situation is a bit more complex than i thought. see i can only change the MAC address if i delete all the previously connected SSID. if i remove the dchp.list will that remove/forget all the previous SSIDs? i would have to run a cmd to forget all the SSIDs prior to running the MAC address change cmd.
I typed busybox ip link set eth0 address XX:XX:XX:XX:XX
i am receiving " bad address"
Pls help me

How to skip WiFi configuration during initial setup of Nexus 7

I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I booted into the bootloader, then used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery ).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)​7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)​
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
organophosphate said:
Allowing The WiFi Setup Step To Be Skipped (Dangerous):
...
9. YOUR TABLET WILL FAIL TO BOOT IF YOU SKIP THIS STEP: adb shell chmod 755 /system/build.prop
...
Click to expand...
Click to collapse
Shouldn't this be 644?
Also, in case anyone wants to know, you can bypass activation after connecting to a WiFi network - you do not need to tie the tablet to your Google account.
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
cwoggon said:
Shouldn't this be 644?
Click to expand...
Click to collapse
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
nextelbuddy said:
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
Click to expand...
Click to collapse
Well, in my opinion, less is more
organophosphate said:
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
IIRC, this would have been helpful to a gentleman who was looking to bypass WiFi activation awhile back. I applaud little workarounds such as this... you never know when this information might be useful.
cwoggon said:
Well, in my opinion, less is more
Click to expand...
Click to collapse
True.
I was dissatisfied with the original approach because of the risk of causing boot failure, so I refactored the implementation to avoid the problem altogether. The updated procedure should be cleaner & more efficient.
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
ehh i still have to disagree with you there. this isn't the same as wanting to install a custom ROM.
installing custom ROMS and Kernels have true benefits whch are optimization and customization that stock does not offer aka more choice.
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice. as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
I know that many custom roms and kernels give me the ability to inccrease speed and add more options in the operating system that i am looking for hence i will choose to flash a new rom and kernel.
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Im not trying to be argumenative just to do it, im trying to determin your real actual justificaton for wanting this besieds "
its my device let me do what i want" because at no point did i say nor did anyone else say they wanted to flash new roms and kernels because it was their device and they wanted to do what they want, they did it because those options benefitted them in a way that the stock experience did not.
Just because someone is on XDA does not man they are here ot hack their device to pieces. there are many reasons people come to XDA..
talk and interact with others that have a love for media devices
ask questions about their devices
learn from others on how to modify their devices
completely change their devices
just to name a few.
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
nextelbuddy said:
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice.
Click to expand...
Click to collapse
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
nextelbuddy said:
as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
Click to expand...
Click to collapse
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
nextelbuddy said:
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Click to expand...
Click to collapse
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
nextelbuddy said:
Just because someone is on XDA does not man they are here ot hack their device to pieces.
Click to expand...
Click to collapse
Then this procedure is obviously not for them. That's perfectly okay.
nextelbuddy said:
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
Click to expand...
Click to collapse
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
organophosphate said:
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
Then this procedure is obviously not for them. That's perfectly okay.
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
Click to expand...
Click to collapse
Im only one person. I can appreciate your work into finding a valid work around and am in no way attempting to take that from you and im sure there will be many that will be happy and thankful with your hard work. Dont take what I said as any sense that this is how the community feels please.
keep on with your work!
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
nextelbuddy said:
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
lex1020 said:
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
Click to expand...
Click to collapse
That's a good reason!
Absolutely agree that you should be able to skip that step. AND no valid reason needed. Unless Google can show a valid reason for not letting you skip that step. I'm sure most of us have watched the Google, (and Facebook) 'net' close in around us. When I started on Android I thought it was so cool how it was all tied to Google and was cross device. Now I'm like: Google would you just get out of my way, I'll be more than happy to click on 'you' when I need something from you.
The latest insult is that annoying "Keep Shopping" prompt in the Play store. Clicking Back, and Keep Shopping does the exact same thing. I shouldn't have to do either. Since I used to be dropped back to the same place anyway.
While the initialization does require a Wi-Fi connection it does not require an Internet connection. I was able to connect to my printer Wi-Fi network and let the waiting bar run for 2-3 minutes then the initialization would continue to completion.
I didn't like this Google forced initial setup either but at least no information was broadcast this way. The Nexus 7 is very useful even when not connected to the Internet.
Chicken and egg
organophosphate said:
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery </path/to/clockworkmod.img>).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)​7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)​
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
Click to expand...
Click to collapse
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
violincello said:
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
Click to expand...
Click to collapse
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That's exactly what I did. I was sitting in a parking lot after purchasing my N7 and didn't have a hotspot nearby. I wanted to play with my tab for a few before heading home so I just fired up WiFi Tether on my Rezound.
Sent from my Nexus 7 using xda app-developers app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Click to expand...
Click to collapse
Absolutely. As I mentioned in the OP, this isn't the fastest solution. Hell, you can probably tell I don't even recommend it for common scenarios.
That said, the approach *does* work. Before I started this I searched and was unable find any other way to accomplish the specific goal of skipping/disabling WiFi connection during initial setup. Therefore, when I was finally able to get it working I wanted to document it for the community.
dr.m0x said:
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I tweaked the OP to indicate this more clearly.
Simply
Andie00 said:
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
Click to expand...
Click to collapse
When it happened to me, i just restarted it. It then booted to the homescreen.

TP Toolbox Media Mount FAILED

I am attempting to install Android via TP Toolbox and am having a similar problem that others have reported. I can load TP Toolbox, but the media mount portion fails and my Windows 7 x64 machine never sees the HP Touchpad volume. Here's the twist:
I have done this 2 previous times with different Touchpads, the same Windows 7 machine, and the same USB cable, and it worked fine. I have already tried a different cable, same results; works on other TPs, but not this one. So maybe it's NOT the cable, as has been the case with the other instances I've read through on this forum. Unfortunately, I don't have an HP OEM cable to test against.
I'm attaching the klog.txt in the hopes a reason can be found in there. Thanks in advance.
ChefDan said:
I am attempting to install Android via TP Toolbox and am having a similar problem that others have reported. I can load TP Toolbox, but the media mount portion fails and my Windows 7 x64 machine never sees the HP Touchpad volume. Here's the twist:
I have done this 2 previous times with different Touchpads, the same Windows 7 machine, and the same USB cable, and it worked fine. I have already tried a different cable, same results; works on other TPs, but not this one. So maybe it's NOT the cable, as has been the case with the other instances I've read through on this forum. Unfortunately, I don't have an HP OEM cable to test against.
I'm attaching the klog.txt in the hopes a reason can be found in there. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem only I have 2 tablets and i installed tp toolbox wiped webos installed andriod on the first it went so smooth I figure why not do both well cause now I have on functional and one thats not Im unable to get webos or anything It boots with option restart webos restore or shutdown and cant get any os on it now but atleast one of mine works great databuilds are the way to go but its a 50 50 chance youll end up with one only good for parts Ive tried aking on the forums where the guy who released tp toolbox but have been denied access for asking questions and no replies. I only got one of them to mount after tp toolbox android install. It is not the cable its not the os win7 cause I tried my two back to back and their the same model# If you figure it out let me know
ddgls08 said:
I have the same problem only I have 2 tablets and i installed tp toolbox wiped webos installed andriod on the first it went so smooth I figure why not do both well cause now I have on functional and one thats not Im unable to get webos or anything It boots with option restart webos restore or shutdown and cant get any os on it now but atleast one of mine works great databuilds are the way to go but its a 50 50 chance youll end up with one only good for parts Ive tried aking on the forums where the guy who released tp toolbox but have been denied access for asking questions and no replies. I only got one of them to mount after tp toolbox android install. It is not the cable its not the os win7 cause I tried my two back to back and their the same model# If you figure it out let me know
Click to expand...
Click to collapse
If as you have stated there is a 50% chance of bricking your Touchpad pad there would be hundreds if not thousands of members posting about it not just 2.
Please read the rules, you cannot post in the developers forum because you have not made 10 USEFUL posts.
The guy as you put it is Jcsullins a highly respected Developer on this and other forums. So how you can expect any help when you haven't even read the rules and slag of the man you has continued to bring life to a 3 year old device that was never intended to run Android in the first place beggars belief.
Have a nice day.
misunderstood
sstar said:
If as you have stated there is a 50% chance of bricking your Touchpad pad there would be hundreds if not thousands of members posting about it not just 2.
Please read the rules, you cannot post in the developers forum because you have not made 10 USEFUL posts.
The guy as you put it is Jcsullins a highly respected Developer on this and other forums. So how you can expect any help when you haven't even read the rules and slag of the man you has continued to bring life to a 3 year old device that was never intended to run Android in the first place beggars belief.
Have a nice day.
Click to expand...
Click to collapse
sorry if you think that I am putting down jcsullins, you obviously cant read between the lines! If I didnt like jcsullins or all the hard work he put into all of this why would I be on here and using these forums and trying to get help from him and all that follow. Im just frustrated that my first touchpad that I used the tp toolbox on wents so damn smooth with little imput or know how to do and took less than 8 min. then I tried my other (identical) touchpad (serial# and all) and couldnt get it to mount,. then I tried reinstalling webos and that failed, tried the hp webosdoctor to reinstall webos I did as described used the volume up to initiate webos restore and the webdoctor connects to it and only runs for about 2-4 min than automaticaly dissconects it , it switches from the usb symble to the hp logo and now I am unable to do anything with it,
I know I jumped the gun a little but in time Im sure Ill be all over this site so forgive me if im a bit frustrated that no one has figured out a solution yet and I thought if I created a little wave to get some attention, and to also help others that are in the same boat im in to let them know they may have done everything as described in the instuctions and still not get the device to mount thus confirming what they already know that its not the cable, not the windows 7 64bit but most likley some internal part of the touchpad maybe the usb port board or the one he designed this all for was a later model with diff guts than the eirlier models hp put out, who really knows. Im thinking of taking mine appart again and swapping the usb board, but wanted to see if someone had a fix for it before doing that again
to jcsullins you dont really need to here me say that I apprecitate all that youve done, you should allready know that by me trusting all your software and installing it in my device, and recomending your site to all my friends and some strangers!! I dont make much $ or I would gladly fork over some. but I work at a car wash hence the no money but I hope maybe one of the people I refer you too might
Not a problem, this is what I used after I managed to completely mess up my TouchPad well over a year ago and it brought it back to life.
http://forum.xda-developers.com/showthread.php?t=1426244
Pay particular attention to the first post on page 12. Also with all the commands use copy and paste as it avoids any possible typo's.
Good luck and all the best.. ☺
sstar said:
Not a problem, this is what I used after I managed to completely mess up my TouchPad well over a year ago and it brought it back to life.
http://forum.xda-developers.com/showthread.php?t=1426244
Pay particular attention to the first post on page 12. Also with all the commands use copy and paste as it avoids any possible typo's.
Good luck and all the best.. ☺
Click to expand...
Click to collapse
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.
ChefDan said:
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.
Click to expand...
Click to collapse
Pretty much the same for me, that is where the first comment on page 12 helped me and everything was done through command prompt.
Good luck.
FIXED!!
sstar said:
Pretty much the same for me, that is where the first comment on page 12 helped me and everything was done through command prompt.
Good luck.
Click to expand...
Click to collapse
And the verdict is... IT WAS THE USB CABLE. Sstar, I poured over your post and the comment you mentioned. All those lvm.static commands are done by TP Toolbox when you choose Install Android, so I couldn't see where that made a difference. But I tried it anyway. I couldn't figure out how to get a terminal prompt using novacom when it would keep losing connection to the machine, so I had to improvise. I had previously created an Ubuntu 12.04 USB boot stick and downloaded jcsullins' tpdebrick to fix one of the two 16GB touchpads previously, so I edited the tpdebrick script to prematurely exit at line 546, right above where it starts copying the A6 firmware files to the Touchpad. Once there I established a TTY session to the touchpad and manually entered all the commands to configure the Android volumes. However, I never could get WebOSDoctor installed as it recommends in the rest of the post, it kept bombing out at 4%, just like before. I think it must be because some folders and files it's expecting to exist on the Touchpad are missing after you do a Complete Data Reset in TP Toolbox. Finally, out of desperation, I loaded TP Toolbox again and chose Mount Media Volume, in the hopes that maybe I could still get the ROM, recovery and gapps files onto the machine and install. Well, it worked. The mounted Volume was not named HP TOUCHPAD as it was supposed to be, but it was there, and I was indeed able to copy the files to the TP and installed CM11.
Then I thought about it some more. So why would it matter that I manually configured the Android volumes? Turns out it didn't. I did all the above using a brand new 6 ft USB to micro USB cable I bought at Office Depot (Ativa Item #833-445, if anybody's interested). I decided to try the whole process again, using one of the USB cables I had previously, and... the Media Volume would not mount. Tried a 3rd USB cable. No mount again. The new cable was the only one that worked. Why did those cables not work on the 16GB Touchpads, when they worked just fine on 2 previous 32GB Touchpads? I have no idea. I even went back and tested the TP Toolbox Mount Media Volume option on the 32GB Touchpad, and both cables still work, but will NOT work on a 16GB Touchpad. I'll leave that for greater minds than mine to ponder.
Learned a few interesting things along the way:
- If you ever need TP Debrick, you will save yourself a lot of frustration if you use Ubuntu v 12.04 vs the current 14.04. The older version will download the abd and fastboot tools for you; 14.04 requires that you find them and install yourself.
- If your media volume fails to mount in TP Toolbox, like if you had a bad cable, you *MUST* reboot the Touchpad and reload TP Toolbox with a good cable before trying it again. It won't work otherwise.
- Using Ubuntu on a laptop with a mouse touchpad is the most frustrating thing imaginable. Use a standard mouse if you want to keep your blood pressure down.
- If you get the 'There was an error communicating with Google Servers' error when trying to create or sign into your Google account when going through the initial setup, set up, (and you don't have 2 factor authentication on your Google account) check the version of gapps and make sure that is named gapps-kk-20140105.zip with a size of 87,179,530 bytes. There is another, smaller version of the same file out there that apparently does not have Google Play Services in it. If you do have 2 factor authentication, you'll need to create an app password for the Touchpad or turn off 2 factor authentication.
Hope this helps someone!
ChefDan said:
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.
Click to expand...
Click to collapse
I also have simular problem when I try to use webos doctor I get it all set up and then I can get it to start running but within 4min the hp logo pops on the device and it disconects itself and then stops running leaving my device useless, Ive tried useing the tp toolbox following the directions to the letter and then running webos doctor and still nothing, I know you guys are alot brighter than me and hope you find a fix soon thanks
ddgls088 said:
I also have simular problem when I try to use webos doctor I get it all set up and then I can get it to start running but within 4min the hp logo pops on the device and it disconects itself and then stops running leaving my device useless, Ive tried useing the tp toolbox following the directions to the letter and then running webos doctor and still nothing, I know you guys are alot brighter than me and hope you find a fix soon thanks
Click to expand...
Click to collapse
This sounds like the exact place I was. I never got WebOS to install; if you did a 'Complete Data Reset' from TP Toolbox, WebOS is gone forever. However, you can skip installing WebOS and just Install Android. TP Toolbox will create the Android voilumes and mount the media volume, where the next step is to copy a recovery ROM, your Android ROM, and GApps file to the TTINSTALL folder on the media volume. Then, Eject the media volume in Windows, and Unmount Media volume in TP Toolbox. TP Toolbox will check the ZIP files and install Android.
ChefDan said:
This sounds like the exact place I was. I never got WebOS to install; if you did a 'Complete Data Reset' from TP Toolbox, WebOS is gone forever. However, you can skip installing WebOS and just Install Android. TP Toolbox will create the Android voilumes and mount the media volume, where the next step is to copy a recovery ROM, your Android ROM, and GApps file to the TTINSTALL folder on the media volume. Then, Eject the media volume in Windows, and Unmount Media volume in TP Toolbox. TP Toolbox will check the ZIP files and install Android.
Click to expand...
Click to collapse
I appriciate the advice but I was trying to reinstall webos or anything cause after I wiped webos with tptoolbox it wouldnt mount so no ttinstall folder to move all of the roms to
ddgls088 said:
I appriciate the advice but I was trying to reinstall webos or anything cause after I wiped webos with tptoolbox it wouldnt mount so no ttinstall folder to move all of the roms to
Click to expand...
Click to collapse
Ddgls088 - OK, just trying to help here. Re-read what has been posted previously. If the media mount fails in TP Toolbox, you've most likely got a bad USB cable. It may work for other purposes, or on other devices but there's something wrong with it. What is happening to you is exactly what happened to me. Buy a new, good quality USB cable and try it again from the top, with the complete data reset, then Install Android. If you have a good USB cable, the media volume will mount. Good Luck!
For those still having issues, please try the version of Touchpad Toolbox (v41) I just released in this post:
http://forum.xda-developers.com/show...&postcount=293
Note that you will need to use one of the new Recoveries linked from that post.
If you still have problems with that version of TPToolbox, let me know in this thread.
Also, for those having issues re-installing webOS after a "Complete Data Reset," see the second
set of steps in this post:
http://forum.xda-developers.com/showpost.php?p=52922166&postcount=64

Categories

Resources