Related
How do I delete ICS from moboot? I HAVE TRIED EVERYTHING!!!
Core droid htc glacier
Fixed'........
rpomponio said:
How do I delete ICS from moboot? I HAVE TRIED EVERYTHING!!!
Core droid htc glacier
Fixed'........
Click to expand...
Click to collapse
Hello
I am new to the xda forums but have been playing wih the roms since alpha stage
I am currently running XRon ICS 0.0.2
I am aware of two ways to lose ICM from Moboot: Adb or terminal commands and through Webos
Adb an terminal commands are not a strength for me, but if you search the Xron forum for moboot and remove CM,the process is pretty straight forwrd (4 or 5 lcommand lines) just adjust for remove ICS
If i can offer the Webos approach, let me know
Edit: try post 6766 in the Xron forum as a start
Go to webos, install internals pro from pre ware, start internal pro, set master mode on from the menu, navigate to /boot, remove uimage file you wish deleted from moboot e.g. delete image.pics to remove pics from moboot. Exit, reboot, enjoy.
Sent from my Touchpad using Tapatalk
***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.
You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk
If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.
link not working
anyone have updated link that works to download this?
yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra
I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk
nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .
I am going to update the post and host the files. There is also some extra stuff i will put up for download.
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse
using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?
BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk
What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5
This worked great.
Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
Is it possible to do this on our touchpad using smackmeinstaller?
Most definitely possible. Currently using it right now. I encountered a few hiccups along the road to getting it there, but the process will remain the same.
First and most important, you'll want to make a nandroid backup so it'll be easy to get back into Android without losing anything. BE SURE to move this to a computer to be safe.
After that finishes, you'll want to work towards removing Android entirely. This can be done with a CMUninstall file found from the CM10 page. Should be run in a similar manner to what Installing Android looked like. This will remove moboot as well as android.
From this point, simply install Ubuntu from the instructions they give on the page. Here's a quick rundown of that. If I'm missing something, follow their word, not mine. Start by creating a sminstall folder and placing the Ubuntu file (larger file size) and the setup file in the folder on your Touchpad. Then set (depending on if you want the alpha kernal or the standard) the uImage file in your palm directory that you uninstalled android from. If all goes well, you should boot straight into webos not seeing the familiar moboot screen. This is ok.
At this point, you'll want to follow the standard instructions to install Android. Place the following files in your cminstall folder:
Rom, CWMrecovery, Moboot(latest is 0.3.8), and be sure to snag some Gapps if you for some reason need to start fresh. Install that using the normal instructions.
Finishing should bring you to moboot with a new option of kexec. This is a "moboot" for Linux options. Use the volume keys to select Ubuntu and press power and home buttons to start it. I HIGHLY recommend a Bluetooth keyboard and mouse for it.
TL;DR - Backup. Remove Android. Install Ubuntu per instructions. Install Android per Instructions. Restore. Profit.
I used this post as a guide in more detail. http://forum.xda-developers.com/showthread.php?p=41464020
Also, I would advise against running WebOs doctor after the linux installation, as you have to do some extra work in order to get the touchpad into working order.
Sent from my TriBooting HP Touchpad using xda app-developers app
nsboot - NinjaSwag Bootloader/Installer
WILL REPLACE smackme2 and kexecboot!
Source: https://github.com/willcast/nsboot
Kernel source: https://github.com/willcast/ubuntu-kernel-tenderloin/tree/kexec (kexec branch, not Ubuntu)
Binary: https://docs.google.com/file/d/0B4WUjKii92l2Ukl4TE1EM1pjTDg/edit?usp=sharing
I have been working on this for about 2 weeks...
Features
Touch screen based interface
Able to boot kexec kernels
Able to install Android and Native Linux OSes, kexec tar files, and uImage kernels
Able to back up entire volumes as .tar.gz (with permissions & ownership)
Directly compatible with smackme and kexecboot config files
Can replace moboot entirely with the touch of a button.
Integrated file browser
Software touch keyboard available
Haptic feedback
uImage is < 4 MiB
Loads 3x faster than kexecboot
Has integrated ADB server so you can push and pull files from any mounted FS, or run a local shell.
Known issues so at this time
Colors are messed up in included TWRP recoveries
Things still to be tested
nothing as of now
kexec images for reference
webOS 3.0.5: https://docs.google.com/file/d/0B4WUjKii92l2WU9fdkNZa0V5NUk/edit?usp=sharing
Arch Linux ARM: https://docs.google.com/file/d/0B4WUjKii92l2YWRFUWJoMkpXRzg/edit?usp=sharing
Ubuntu: https://docs.google.com/file/d/0B4WUjKii92l2MXlEVmxQUHoyUzg/edit?usp=sharing
Slackware: https://docs.google.com/file/d/0B4WUjKii92l2MnRwMGRyTmRQcW8/edit?usp=sharing
Fedora untested: https://docs.google.com/file/d/0B4WUjKii92l2S3pVUkZNNzNSQUU/edit?usp=sharing
Android 2.2 Froyo: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3 Gingerbread: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0 Ice Cream Sandwich: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
How to test
Code:
novacom boot mem:// < uImage.nsboot
To install, copy it to /boot (/dev/mmcblk0p13). It can also install itself if you put a copy of it on the SD card, and go Installer menu -> install uImage and navigate to it.
Screenshots are attached.
YouTube demo of a earlier version with only the boot working and a simpler menu: http://www.youtube.com/watch?v=0oQhSa4sqPU
Updates:
All OSes now boot (At least on my TP.)
Those which have had their kexec archives revised on GDrive since the first post are in italic.
Android 4.2
Android 4.1
Android 4.0
Android 2.3
Android 2.2
Android Recovery (included with all Android kexec archives)*
webOS
Ubuntu
Slackware
Arch Linux
Fedora
* The colors are still out of whack in recovery. It's mostly unneeded at this point with Built-In ADB support and zip installation, but I included it for those who want its more obscure or advanced features, or are more comfortable with its UI. Testing it specifically is appreciated because I don't have any plans to develop a test suite for it.
Compatibility list
Android ROMs
4.2
There is currently an issue with installing later Android 4.2 ROMs. The following 4.2 ROMs will install and boot:
Evervolv nightly 05-15-2013
The following 4.2 ROMs get stuck in a fairly serious bootloop (logcat shows at least surfaceflinger, mediaserver, and zygote segfaulting). I have tried different kernels.
CM 10.1 unofficial nightly 06-02-2013
Schzoid 2.0 nightly 04-23-2013
Other 4.2 ROMs are untested.
4.1
The following Android 4.1 ROMs have been tested and work:
JCSullins' CM 10 preview, 12-16-2012
Schzoid 1.2, 03-06-2013
4.0
The following Android 4.0 ROMs have been tested and work: CM 9 nightly, 01-06-2013
2.3
The following Android 2.3 ROMs have been tested: CM 7 Alpha 3.5
Issue: When the screen is woken up in CM7, nothing shows up on the display. The backlight does turn on.
2.2
The following Android 2.2 ROMs have been tested and work: my Froyo kang, version 0.4 and 0.3 (0.4 is on google drive on top of 0.3)
Native Linux
Ubuntu
The following Ubuntu releases have been tested and work: Ubuntu 13.04 final, Ubuntu 12.10 final.
Others are welcome to be tested, but I will probably not take issue with anything before 12.10 beta not working.
Arch Linux
Arch Linux boots, and seems to work. Wi-Fi has not been tested.
Slackware
Slackware boots and seems to work. Wi-Fi and Bluetooth have not been tested.
Debian/Bodhi
I am unable to locate any tar.gz archives to test for this distribution, nor a kernel of any sort. If anyone wishes to step up and send one to me or even host it, I would be grateful and also I'd probably get it booting within a day.
Fedora
These haven't yet been tested. They are theorerically installable with the new "tar.gz to custom LV" feature, but I would need to find a way to free more space on my TP to install them (my media partition is currently about 10 GB, 6 GB used for music, and 2.5 GB used for testing files.
Thank you
Good Job! I will test it tomorrow.I have been looking forward to ArchLinuxArm for a long time.Thank you.
Looks really good, I'll give it a spin.
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Same here! But i Can Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
After I made the webOS image, I noticed that it's a bit... finicky. Just reboot from nsboot main menu. Then try loading webOS again.
If you need to get to recovery mode, the way to do it is to reboot like that, holding down VOLUME UP.
imapjonny said:
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you installed CM to the logical volumes named /dev/store/cm-*, you need to back up and reinstall it from nsboot. As for booting CM recovery from nsboot, if you haven't done that yet, a feature I put in already lets you make .tar.gz archives from volumes (including Android ones.) I just enabled the extraction of them to Android volumes (used to only allow others), so you could use that to "move" your Android.
Minimum System Sizes to use for android partitions:
2.2 (froyo): 256MB
2.3 (gingerbread): 320MB
4.0 (ics): 320MB
4.1 (jellybean): 450MB
4.2 (jb mr1): 480MB
Step by step instructions:
Upgrade nsboot. Just released a new one. Either scp/adb it from a running OS or redo the install procedure except for the replace moboot part, after downloading it again.
Get the kexec tarchive for your android version onto the SD card. You could scp or adb push it. If needs be, find your old Android recovery image, and boot it via novacom:
Code:
novacom boot mem:// < uImage.ClockworkMod
Boot nsboot.
Go to Utilities - create volume tarchive.
Select "cm-system". Name the backup "System".
Repeat last two steps for "cm-data" if you want to keep your data partition. I don't recommend backing up "cache".
Go to Utilities - create volume set.
Name the new Volume Set depending on your Android/CM release: Use the names "android22", "android23", "android40", "android41", or "android42".
Format the new volume set: go to Utilites->format volume set, and select it. Click Confirm/OK.
After the set is created, go to Installer menu -> install .tar.gz to existing volume. Navigte to /mnt/media/nsboot/backups. You will find your two backups. Select "System" to restore to "androidXX-system", depending on the version you just created. Make sure you use a big enough size - see above table.
Repeat the last step for data, if you made such a backup.
You now need to find the kexec archive you copied to your SD card (it's mounted in /mnt/media.) Install it. If you chose the right volume set name, it will work.
Reboot or rescan boot items and you should see the Android version in your boot menu. Tell me if it doesn't work.
If it does work, go to utility menu -> delete volume set and select "cm" as your set. This will remove the old cm set, and leave the new androidXX one.
After that, if it did work, go to utility menu -> reclaim media space to get back any lost space for your media/sdcard partition.
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
imapjonny said:
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
So when you guys who are having trouble with webOS try launching it, do you get to the screen that says 'please wait, booting...' or the HP logo that pulsates? Where does it reboot? I'm thinking I might have uploaded an old, non-workable tar file for that OS.
FYI: After testing every boot option, I discovered a problem with Android 4.1 (only 4.1). I'm looking into it.
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
superboy123 said:
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
Click to expand...
Click to collapse
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
castrwilliam said:
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Click to expand...
Click to collapse
Okay everything is working well with this new tar.
Sent from my GT-I9300 using xda app-developers app
Make sure your pad is fully charged. I have had problems before during partially charged tp
John 3:16
castrwilliam said:
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
Click to expand...
Click to collapse
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Okay, try the volume up button. If that doesn't work, try holding power + volume up + home (rebooting it), ignoring the boot loop. I only said to delete one uImage... wait, uImages are the only files you deleted, not anything else in /boot, right?
Do you ever see the HP logo?
If you touched "boot.bin" (among certain other possible files in /boot) you'll probably need the debrick program. This isn't nsboot's fault... link to program is here: http://forum.xda-developers.com/showthread.php?t=2010270
If you use that program, follow its instructions TO THE LETTER, if there is anything you need clarification on, ask here - I've never had to use it, but I've heard of it fixing TPs that don't even show anything on the LCD. That said, if something goes wrong with it, it has the opportunity to make the problem far, far worse.
castrwilliam thank you for your work
Rock on dude
loving your work man keep it up dude:good:
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Is the pad fully charged? I would strongly suggest letting it charge for twenty four hours.
P.S. don't panic
Sent from my Galaxy Nexus using Tapatalk 2
Is it possible to install Ubuntu 13.04 and 12.10 at the same time?
Sent from my GT-I9300 using xda app-developers app
I am a little confused on the install process, would you mind elaborating.
Sent from my Galaxy Nexus using Tapatalk 2