Database Users

No instant root for Hero under 2.1?

There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?

rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.

Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.

Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!

Ok. I'll try later as the villainrom web site is not reachable now.

rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735

rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.

pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse

Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.

Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?

Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?

If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.

You are the best. Thank you.

Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598

[GUIDE]Install Android SDK and upgrade Marketplace to 2.2.6

FIRST OF ALL, I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICE! PROCEED AT YOUR OWN RISK!!!​
Now that we got that out of the way...
I have noticed that some people`s Marketplaces simply refuse to update by themselves (exactly what happened in my case) and as most of the people visiting this forums are not tech-savvy and simply want a step-by-step guide to get things working, I decided no harm can be done by me posting this info.
Installing Android SDK revision 8
First of all, you will need to have Android SDK (and ADB of course) installed with the drivers ready to go. In order to get the SDK installed go to the official Android website and download the latest revision (r08 at the time I posted this). You can download any of those files, but I prefer using the executable installer so I can make sure everything is at its place. Now, there are two major flaws with this whole process which have almost made me quit the whole process several times, but I got them sorted out and will help you solve them aswell.
FLAW #1: After beginning the installation process, the installer will prompt you to download a JDK (Java Developer Kit) in order to continue installation. Hit the "Visit sun.java.com" button and download the latest Java SE (currently this one). But before proceeding be sure to download the 32 bit one, as the Android SDK only recognises this version. I know it`s not a big deal, but I spent about two hours trying to figure out what the heck went wrong and it became quite frustrating.
Install the JDK, then the SDK. Once Android SDK is done, simply go ahead and launch SDK Manager (you can find it in Program Files\Android\android-sdk-windows\) and when you get to choose the packages to install, simply check "Accept All" and click "Install". Once it`s done, it`s time to download the drivers. Click "Available packages", tick "Third party Add-ons" and under "Google Inc. add-ons" you should find "Google Usb Driver package". Tick it and click "Install". IF YOU GET AN ERROR SAYING THAT PERMISSION WAS DENIED AND YOU ARE UNDER WINDOWS 7, COPY THE WHOLE "Android" FOLDER CONTAINING THE SDK TO YOUR DESKTOP (OR ANY OTHER PLACE) AND REPEAT THE STEPS ABOVE. I know it`s quite rudimentary, but it does its job. Once it`s done, a folder named "google-usb_driver" will be created under Android. Be sure to correctly copy it to the original location in case you had permission issues.
FLAW #2: Ever since Android SDK r08, Google decided to remove the ADB files so now they have to be manually placed in the folder. I have uploaded them for you, so click here to download them. Once downloaded, extract the archive to the "Android\android-sdk-windows\tools" folder.
OPTIONAL: Go to Start Menu, right click on Computer, click Properties. The System window will appear, where you need to go to "Advanced system settings". Once there, click on "Environment variables" and where it says "System variables", look for PATH. Once found, highlight it and click "Edit..." then add the line "C:\Program Files\Android\android-sdk-windows\tools;" at the end. Click "Ok", "Ok" and "Ok", then restart your computer.
Right now everything should be working as expected. Connect your HD2 to the PC via USB and hope for the best. If the drivers are working and it is recognized as a HTC device, open a command prompt and type "adb devices". If you get anything such as "List of devices attached" followed by some code such as "0123456789ABCDEF device", everything is working well. Good job, you just correctly and completely installed Android SDK on your PC!
If not...
Check your device manager and if you see any devices related to your HD2 having problems, simply right click on them and update the drivers with the ones downloaded earlier in the "google-usb_driver" folder then reboot your computer.
We`re all set! ...What now?
The whole process is actually quite simple. First of all, download the new 2.2.6 Marketplace and put it somewhere accessible, such as your desktop. Open a command prompt and enter the following:
Code:
adb remount
adb shell
rm /system/app/Vending.apk
This will basically delete the old Marketplace from your device.
Now go to the folder where you placed the new Marketplace, hold down Shift, right-click and select "Open command window here". A command prompt should pop up at the exact location. Now execute the following command:
Code:
adb push Vending.apk /system/app
And that is it! Now restart your device and try to run your Marketplace, it will load for half a minute or so then it will start normally. Enjoy!
I know this is rather a tutorial for installing the SDK, but I figured it would be useful to let everyone know how I managed to solve my problem. In case I skipped any steps or you notice anything wrong/wish to add anything, please feel free to do so!
If you feel my post has helped you in any way, do not hesitate to hit the "Thank" button!

Reserved post for further mini-tutorials.

At least on my r08 install if you install the platform tools component then adb will be available under the platform-tools directory (moved from the tools directory).

@OP
Did you test this on a non sense build?

This procedure will most likely not work with Cyanogenmod ROMs. That and I'd suggest you give the newest market version (2.2.7) instead. I'm not willing to destroy my ROM again by trying it on CM.

[ANDROID] ClockworkMod Permanent Installation Fix! - Step by Step Instructions

I have figured out a way to permanently install ClockworkMod Recovey on your hybrid WebOS/CyanogenMod Touchpad. Like many of you, my ClockworkMod installation failed when I tried to install using ACMEInstaller while I also installed CyanogenMod.
I realize there is now a workaround to "inject" ClockworkMod into your TP using novacom however this requires you to utilize a computer everytime you want to boot ClockworkMod. Follow the instructions below to install ClockworkMod onto your TP permanently and free yourself from your PC!
1. Boot into WebOS
2. Mount TP to your computer and create a "cminstall" folder if it no longer exists after your CyanogenMod installation
3. Copy the "update-cwm_tenderloin-1012.zip" file into the "cminstall" directory, then unmount TP from computer
4. Download the "Internalz Pro" program using the "Preware" application in WebOS if you haven't already (Google is your friend if you get stuck here)
5. Open "Internalz Pro" and navigate to the "boot" menu (will most likely require you to tap the top-most icon of a folder with two dots next to it to get to the root of the TP - should be second folder down)
6. Tap on the file "uImage.ClockworkMod" and select "move"
7. Navigate to the "media/internal/" directory and click "select" to move file
8. Now tap on the file "update-uimage" and move the file to the same "internal" directory you did in step #7
9. Exit from "Internalz Pro" and reboot device while holding down the up volume key, which will take you in to WebOS Recovery (or select WebOS Recovery when you get to the moboot screen you may have previously installed) - you should now see a large USB icon and should be connected to your computer using a usb cable
10. Go to your command prompt in Windows and navigate to the menu where you have novacom installed - you should also have the ACMEInstaller binary file copied into this directory by now (If you don't know what I'm talking about, remember Google is your friend)
11. Type in "novacom boot mem:// < ACMEInstaller" in the command line and press enter
12. You should now see ClockworkMod recovery installing on your TP - Once it reboots into moboot select "boot ClockworkMod" and watch it boot into ClockworkMod!
13. After celebrating, boot back into WebOS, go into "Internalz Pro" and move the file "update-uimage" back into the "boot" directory - the "uImage.ClockworkMod" file that you put in the "Internal" directory is no longer needed since you reinstalled ClockworkMod properly
Essentially the boot directory was overloaded which caused for insufficient space when installing ClockworkMod. Now you should be able to boot into WebOS, CyanogenMod, WebOS, AND ClockworkMod Recovery without a computer. As always, I do not take responsibility for you bricking your TP or variability you may have... use this information if it is helpful but don't blame me if something goes wrong. I'm just trying to help out the community that has helped me for so long.
Let me know if this is helpful to you. Thanks!
dseelye

What!?
Hi!
firstly, thank you for making this guide, i know that alot of people like myself will appreciate it.
but i've run into a problem, see, now i don't have the option to boot into cyanogenmod anymore !
can i flash it in clockworkmod, or do i have to do it all over again?
a reply would be appreciated

you most likely copied the wrong file from the boot folder, as there was one for clockworkmod and one for cyanogen mod... look and see if you incorrectly copied the cyanogenmod "uImage.CyanogenMod" to your internal sd card to free up space. You will have to move this back to the boot folder and grab the other one.

Thank you VERY much!
and thanks for the INCREDIBLY quick reply!
EDIT: IT WORKED!!! YOU'RE THE MAN!!!!!

No problem... let me know if that solved your concern...thx
EDIT: Oh, just saw the edit of your post...great, glad that was it!

Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?

Yes, I just mean that you don't have to "inject" clockworkmod into your TP using your computer which was the workaround for the people who couldn't get it installed originally during the CyanogenMod installation. This just installs it properly but can be wiped with WebOS Doctor like anything else...

bigblueshock said:
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Click to expand...
Click to collapse
Yeap... it will not delete a single bit of CM7, just gonna restore the original bootloaders, delete moboot and skip CWM /Android on boot...
Running again ACME with only moboot and CWM in the cminstall folder will restore them.
....After WebOS doctor... it will show CM7 as the last time you shut it down.
Sent from my GT-I9000 using XDA App

I followed directions exactly but I am not seeing the uImage.clockwork in the boot folder. Any suggestions? I see that file in the cminstall folder, do I just leave in there or should I copy directly to media\internal?
Sent from my SPH-D710 using xda premium

The "uImage.ClockworkMod" may not be in the boot directory I suppose if the previous install attempts didn't put it there so not sure why it isn't in yours. Essentially you are just trying to move some of the larger files out of that directory so you can install ClockworkMod properly as the space constraint of the partition size seems to be the issue. The other file I mentioned, "update-uimage", is actually the largest one I found and you may be able to do the ClockworkMod install properly by only removing that one temporarily. Let us know if you are able to resolve.

I've installed clockworkmod recovery with no errors on the first try, is it advisable that I need to use this method?

I was installing cwm for the first time. I didn't include it originally with the install of cyanogen mod, I guess that's why it wasn't in the boot folder. I placed both files in the media\internal directory and also inside the cminstall folder and ran the command and it worked fine. When I checked internalz pro to remove the files, the cminstall folder and uimage files were gone already. So it looks like I am good to go. cwm is working, I flashed gapps from it. Thanks for reply.
Now I just need to figure out how to make phone calls.
Sent from my SPH-D710 using xda premium

If you installed ClockworkMod completely the first time and it works, then you definitely don't need to do this as this thread was intended for those that tried to install it at the same time as when they installed CyanogenMod and ClockworkMod Recovery didn't install properly. These instructions are to outline how to get it installed correctly as just trying again using ACMEInstaller wasn't working for anyone due to the small size left in the boot directory.

hey thanks for the fix but after the fix i cant get into the market

Not sure why you can't access the market...no issues here. I would suggest reinstalling the gapps zip file and possible the market fix file that are out there now that you have clockworkmod working properly.

thanks for the help thats what i had to do

Hi, the "move" option isn't available, only "copy" "info" and "open"
The entire directory is "view-only"

Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.

Move command
dseelye said:
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Click to expand...
Click to collapse
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.

Thanks
Awesome man! Been struggling with this since two days. Thanks a lot for the fix and step by step instructions
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
tmkhan said:
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Click to expand...
Click to collapse
After Opening "Internalz Pro", Open "Preferences", scroll down to the bottom. You will see an option called "Master mode". Turn it on. You will get read/write access to the boot folder.

[GUIDE][Update][Android CM Alpha 3] How to Install CM Alpha on Touchpad

NOTE: I don't have a TP anymore, but i am pretty sure the installation instructions will be the same moving forward. If you are new follow the full guide, if you are already on one of the CM versions, skip to step 7 and replace the file with the current file.
Note: If you are already on CM Alpha 1/2.1 skip to step 7, if not you can follow the instructions below to install CM Alpha 3 from WebOS.
Alright, here is a step by step instruction on how to install CM Alpha 3 on Touchpad. I did notice there is a video guide but a text step by step might be useful for some. I have this installed and for Alpha release this is fantastic.
Pretty straightforward installation, but as always you follow this guide and flash at your own risk. Main thread for the CM port is here. Read whats working and whats not working there. If you have any questions, post it there. but read the known issues first, don't post know issues. This is just a guide.
Required:
1) PC ( windows, mac or linux) with working Internet
2) HP Touchpad ( obviously) and the usb cable that came with it.
3) Good Reading skills ( I am serious).
4) Read this guide twice if you have to.
Step 0:
Get your pre flash jitters out and think twice. This will root your device and hence your warranty will be void after the flash. If you still want to flash, back up your current HP touchpad. figure out which way is your volume up button ( you will need for step 4) and proceed to step 1
Step 1:
Make sure you have atleast 2GB of free space in your touchpad. Download the following files from here
1)Moboot bootloader for multi boot
2)CM Alpha 3
3)Clockwork Mod Recovery
Once done, go to step 2 below;
Step 2:
1)Acme Installer from here
2) HP WebOS SDK for windows, mac or linux
3) Follow the links above to install the full SDK or just the Novacom driver which is all that is required. If you are not sure, install the full sdk.
on to step 3 now.
Step 3:
1) Connect Touchpad to PC with the usb cable that came with it and select Usb Drive option.
2) Once the Touchpad pops up on your screen, create a folder called cminstall and put the files you downloaded in Step 1 there.
3) Eject/Safely remove touchpad from the pc, remove the USB cable from pc and shutdown touchpad, then go to step 4.
Step 4:
1) Do you know which way is your volume up button? if you are not sure then you are not paying attention to this guide. To figure out which way, boot to webOS, figure it out and shutdown.
2)Hold the volume up button and press power button simultaneously. You should see a white USB symbol.
3)Connect the USB cable back to pc and if the Novacom drivers were properly installed, the driver will be automatically detected and installed.
Step 5:
Almost there, time to install now.
Extract the Acme Installer you downloaded in Step 2 to your desktop or wherever you want. Open up cmd ( in windows) or terminal ( in linux or mac). cd to the directory where you just extracted your Acme Installer.zip and go to step 6 for install.
Step 6:
Now type this in the command prompt after you have done cd
novacom boot mem:// < ACMEInstaller
NOTE: windows users might have to manually move the novacom.exe and/or AcmeInstaller into c:\programfiles\palm folder and run the above command from there.
and wait for it to install and boot into CyanogenMod. If your clockwork mod didn't get installed, go here for a fix.
Step 7:
Update from CM Alpha 1/ 2.1
1) Download CM Alpha 3 from here
2) Plug in your touchpad to PC, select copy usb files option
3) Transfer CM Alpha 3 zip file into the "sd card" of your touchpad when it pops up and disconnect.
4) Long press power button and select reboot, then recovery option.
5) Recommended but Optional ( I didn't): In CWM recovery, go to backup and storage, do a nandroid backup before updating, back to main cwm recovery, wipe cache and in advanced wipe dalvik cache.
6) In the CWM recovery meny, use your volume buttons and select install zip file from sd card, select zip file and select cm alpha 3 zip, then scroll down and say yes.
7) Reboot. To check if you are on alpha 3, go to settings, about tablet and mod version should be alpha3.
To install google market and google apps, go here
Have Fun. Thanks to the awesome CM team, we have android on touchpad.
NOTE: If you want to uninstall CM for whatever reason, download ACME uninstaller from here and run it like you did with ACME installer. This should work ( i haven't tried it though).
SOD( Sleep of Death): This is when touchpad goes to sleep and wouldn't wake up, don't panic. Doesn't happen often and I have never seen it since installing Alpha 2.1. Press and hold power and home button for 10 - 20 secs and your TP will reboot. One fix for this is to use no-frills cpu control or set cpu and set min cpu to 384Mhz.

sticky this!

Good effort but you're going to get warned/banned by the mods for cross linking. They have to protect their domain you know.

techspecs said:
Good effort but you're going to get warned/banned by the mods for cross linking. They have to protect their domain you know.
Click to expand...
Click to collapse
Cross linking? I linked directly to the other websites which host the files. Thats not allowed? If so, mods can delete this thread. Only trying to help. I don't see another thread for a guide here in this section unless i am blind .

I've followed all the steps exactly and I'm getting this:
The ACME files were extracted to my users folder.

RavenSEAL said:
I've followed all the steps exactly and I'm getting this:
The ACME files were extracted to my users folder.
Click to expand...
Click to collapse
Looks like novacom wasn't installed properly. I don't have windows, so hopefully somebody else can chime in. try reinstalling novacom or the entire sdk.
Sent from my HP Touchpad using xda premium

reinstall and a quick reboot on my PC did the trick , running CM7 now

RavenSEAL said:
reinstall and a quick reboot on my PC did the trick , running CM7 now
Click to expand...
Click to collapse
Glad you got it sorted out. Enjoy cm
Sent from my HP Touchpad using xda premium

Android is unable to establish a reliable data connection to verify your google account :|

I am getting the same error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Damian>cd c:\Users\Damian\desktop
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop> novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>Acmeinstaller
'Acmeinstaller' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>
I reinstalled Novacom and in device manager it's there and installed correctly.

Breakthecycle2 said:
I am getting the same error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Damian>cd c:\Users\Damian\desktop
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop> novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>Acmeinstaller
'Acmeinstaller' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>
I reinstalled Novacom and in device manager it's there and installed correctly.
Click to expand...
Click to collapse
Sorry, are you saying when you reinstalled novacom everything worked? if not try moving ACME installer to the novacom directory and try from there.

Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.

Breakthecycle2 said:
Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.
Click to expand...
Click to collapse
try running cmd prompt as an admin. I don't have a windows machine, so i am not sure whats happening with yours. you have xp or windows 7 or vista?

Breakthecycle2 said:
Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.
Click to expand...
Click to collapse
I had problems running it from desktop as well. got the same message you did. tried running it as admin and from c:\ to no avail. put acme in C:\Program Files\Palm, Inc\ directory and it worked finally

I got it! Thanks!

Breakthecycle2 said:
I got it! Thanks!
Click to expand...
Click to collapse
it worked for you by putting it in the palm folder like the poster above yours said? if not please post your soln for other windows users benefit. thanks

im having problems within cmd, i get access denied anytime i run the novacom command, i also ran under an admin account and as administrator n have the same problem, i tried under safe mode and it couldnt connect to server so what do i do?

I am using a laptop using ubuntu 11.04 lts. I follow all of the steps 100% and yet when i do the novacom prompt in terminal it boots my touchpad yet never goes to the penguin screens or installs anything. It just stays on the HP logo untill i do the manual reboot by holding home and power. Any ideas?

rizdog23 said:
I am using a laptop using ubuntu 11.04 lts. I follow all of the steps 100% and yet when i do the novacom prompt in terminal it boots my touchpad yet never goes to the penguin screens or installs anything. It just stays on the HP logo untill i do the manual reboot by holding home and power. Any ideas?
Click to expand...
Click to collapse
did you install the sdk and the novacom driver like the linux link suggested? i have ubuntu 11.04 and the steps i described worked no problems. reinstall novacom drivers

i installed the driver but not the full sdk cuz i was told i did not need to. Can you maybe give me a break down of how things will look like on ubuntu strictly? Sorry if i seem like a noob or it is bothersome for you to have to reply. I greatly appreciate your help

Guide for SBK1 Install of [Win32/64][Dual Boot] Tubuntu for x3Maniac Thread

This guide was written to provide more specific information for installation instructions than the OP below.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
OP for Tubutnu by x3maniac
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.​2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.​4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.​5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.​6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.​9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.​10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.​12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.

Instructions for installing new kernels for SBK1.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.​2. Download the updated kernel from the OP.
a. Extract the .img file into the \bins directory of the installation application. You do not need to rename it because the command you enter in step 3 part b indicates the name of the kernel file.​3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 6 whatever_the_kernel_filename_is.img
c. The filename is the name of the kernel you extracted and copied into the \bins directory. This name can really be anything so long as the command you enter reflects that filename.​4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go​5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android. Boot to Linux now.
6. Download the supplemental kernel file to the root of your filesystem That is the / directory.
a. Open terminal and type this and press enter: sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
b. Then type this command and press enter: sudo tar zxvf /kernel_sup.tar.gz
c. This supplemental is installing modules and drivers to the appropriate locations.
d. Reboot.​7. Please understand names of files especially the kernels and updates will change periodically. The commands and methods of extracting have not changed at this point so substitute the appropriate filename and you should be good to go.

For SBK1 devices, the installation of a custom Android ROM using recovery is very similar to updating the kernel instructions in the post above.
Instructions for installing custom ROM's for SBK1 with Lubuntu installed.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.​3. Copy the file cwrrecovery.img to the \bins folder.
a. You should be able to substitute a newer recovery file than what comes with the Tubuntu installation application.​2. Download the zip file of the custom Android ROM you wish to install.
a. Copy it to either your Internal SD card or External SD card. Depending on the recovery version you flash you may not be able to use your Internal SD card.​3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 cwrrecovery(orwhateverfilenameyourrecoveryis).img
c. The filename cwrrecovery.img is the name of the recovery that comes with the installer application. Please substitute appropriately if you are going to flash a different recovery application. You can also use TWRP just use the appropriate .img file name.​4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go​5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android.
a. Now you want to boot to the Android recovery. Do that by powering off the tablet and booting like normal into recovery mode. This should be volume down and power. Hit volume up when prompted to do so. Flash your ROM according to the ROM owner's instructions. I recommend to complete your ROM's installation set up before proceeding to step 6.​6. You must now flash your Tubuntu Linux kernel back or you will not be able to boot into Linux. Follow the instructions again from the \bins directory using the command prompt and putting your tablet back into APX mode which is volume up and the power button until the Tubutnu installation application shows green for APX Detected.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 whatever_the_kernel_filename_is.img
c. Type this command and hit enter: nvflash -r --go​7. You should now be back into your Android ROM again. From here simply power off and boot into recovery using volume down and power. Then hit volume up when it says to on the screen. If Linux boots without issue then you have successfully reinstalled your kernel.

I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
Click to expand...
Click to collapse

sainthout said:
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
Click to expand...
Click to collapse
0.4.7 fixes the issue with sbk1 and you don't have to do it with these instructions anymore.
However I did try the newer kernel and got stuck at the same spot you did using my instructions just before the 0.4.7 was uploaded. Go to the original thread and post the issue there.

Thanks for the quick reply! Will post the issues

Outdated Thread But Valid Information
This thread is now outdated. X3Maniac has updated his Tubuntu installation application (0.4.7) to fix the issues with installing kernels and recoveries for SBK1 devices.
The information in this thread is still valid for behind the scenes and you can still use the wheelie and nvflash as standalone items if you wish to do something with your device outside the scope of the main thread.
Thanks for all the thanks from users!

Found a bug with 0.4.7. It's possible the tab may not reboot into Prime automatically with this version. When the dev has time it will get updated. If it doesn't reboot and the Tubuntu application says everything is done, manually hold power and let it reboot to Prime to finish installation.

question..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.​2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.​4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.​5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.​6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.​9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.​10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.​12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Click to expand...
Click to collapse
i just succeeded dual booting into ubunto.the prime rom just booted...can i install eos jb rom and still dual boot to ubuntu? thanks in advanced

Yes you can. You will need an updated recovery .img file that supports jb. You temporarily flash the new recovery boot into it then install the new rom. See my post on installing updated android roms. Its the third one I think.

oh sorry for the silly question,,i got it now thanks a lot.. nice job

Hi there,
First off, thanks for the tutorial and hard work!
I've been able to successfully install Lubuntu v1.2 and Lubuntu V1.1-rc1 but I've run into issues with both that I'm hoping you can help me with.
When I installed v1.2, my wireless adapter didn't work and I wasn't able to copy any files (kept saying I was out of space, probably a mounting issue).
When I installed v1.1-rc1, things seemed to work well (wireless worked) but when I tried to upgrade the kernel to 3.1 following the instructions, my mouse pad stopped working and so did my wireless adapter again. I saw that there is a way to fix the mouse pad but it seemed to require an internet connection. Any idea what I did wrong or how to fix the wireless on either v1.2 or on v1.1-rc1 with the 3.1 kernel?
Thanks!

You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/

TomTcom said:
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
Click to expand...
Click to collapse
Awesome, works like a charm. Thanks again!

Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!

Treizy said:
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
See KingZaks post for sound settings. It's in the op and his signature.
The clicking shouldn't do that every time. Did you extract the supplemental zip and are you using the 1.2-1.6ghz kernels?

Hmm, I'm thinking of installing fresh to see if things get fixed. Is there a way to do that without touching the Android partition? I don't want to have to reflash EOS and what not. Do I just not include the Prime img in the images folder?
Thanks!

A Terribly Confused Noob!
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky

TheArtfulDodger said:
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
Click to expand...
Click to collapse
Hey Sparky, there's no more active development on this just so you are aware. That means you can make your own images for newer Linux builds if you wish but things such as hardware acceleration and kernels will not be updated.
In step 1 of my guide you are going to the OP link by the dev who made the Windows based Tubuntu application.
Go to where you see these links:
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
Download tubuntu v0.4.2beta (78mb).
Download tubuntu v0.4.7 (1mb).
Extract the files to whatever location on your Windows machine.
The 1mb file is a replacement of tubuntu.exe file. So just copy/paste and overwrite that file on your Windows machine.
Do you know how to put your tablet in APX mode? If not, you open tubuntu.exe (you might need .net 4.0 Microsoft framework to run the tubuntu.exe). With the tablet off and usb connected to your windows machine, hold volume up and power. The application tubuntu.exe should have a green indicator that it's connected. Change the dropdown to sbk1.
From there you can choose how you want to flash, such as android as the default boot and linux as the secondary boot.

Ignore.