Related
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that
heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.
kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.
You betcha....as always, just sharing information whenever I can.
am i suppose to get a conformation in shell if the commands worked?
Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.
I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...
completed all steps but everything still saves to internal memory
JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.
it works great thanks!
hi dnanj
thanks for the link
sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated
I didn't really know where to put this question, but since it involves my Nexus One I put it here. I put Ubuntu 10.04 on a old Compaq V2000 laptop that I resurrected from the dead, and it's running beautifully. I spend more time on my Ubuntu machine then my new Toshiba/w/ W7. Anyway I need things working like I have on my Toshiba. I set up ADB after getting bits and pieces of information here and there, I just could never get fastboot to work for my N1, except when I'm in fastboot and I plug in my usb it changes from fastboot to fastboot usb, so it's recognized in fastboot, well sorta. But, when I run fastboot devices the terminal just hangs on >>waiting for device<<. Now I have another problem, adb works just fine, but yesterday I used it and where the number of your devices appears is blank now, no number shows up, but I can still run commands. I've done just about everything and I'm at a loss here. Some real help here, no snide remarks, and no [email protected], I need dev help or someone familiar with Ubuntu 10.04, or if you've had this problem lend some help. Once again I already have adb setup, but my number isn't showing anymore, and I need fastboot working, and yes I gave it executable permissions, I exported my path, I created my android rules, I edited my .bashrc file. Thanks much in advance. Long Live Linux!!!!!!
I'm good, found a executable script that solved my problem.
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Read Read Read!!!!!!!!!!
evilkorn said:
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Click to expand...
Click to collapse
I said in my post that I used a executable script, I mean thats all you should need to know. I read about it somewhere, that's all I needed to know, and I found it on my own. They have nuff post on how to setup your adb, but none are 100%, so you have to take bits and pieces from them, and kinda wing it from there. I don't sudo adb on my system, sudo adb =can't be found. It would be senseles to have to type sudo every time you wanted to run adb, I have my to autostart as root as soon as I run adb. If someone needed help all they have to do is ask. Since this post I've had to re-install ubuntu 3 times and I've gotten my adb & fastboot working with the same method I used the first time. I have my adb setup where I can push and pull from any directory, so I don't fill up my tools directory with too many files, and so I don't have to move files, I can just push & pull to & from anywhere.
Perhaps you can share the script you found?
Dude, chill out. The guides are fine and 100%. I don't need to know ****, I know how to setup adb. How the hell is someone going to find that script when you didn't link it.
First, you have to tell sudo where to look for adb, you obviously didn't link it init.d or some other way to tell the software what to do with adb. You have to do 'sudo /home/name/sdk/tools'.
google query: somewhere executable script ubuntu adb
rm -r -f /
Hope this helps
prettyboy85712 said:
Perhaps you can share the script you found?
Click to expand...
Click to collapse
Here's the links, the script isn't mine to give, and I think that would be against the rules. Go to the first link to get the installer, and the next one to get the fastboot exe. I would follow the instructions in the second link. Once you finish that, run the adb script, If nothing pops out of the script when it starts to run , run it again, or try running (in terminal) command. If you need detailed instructions PM me, it's a little process, you have to edit some files.
http://www.droidforums.net/forum/hacking-help/38186-linux-sdk-adb-autoinstaller-script.html
http://forum.xda-developers.com/showthread.php?t=537508
Good for you.
Hi,
it's my first post here and I'm aware that I'm going to ask a typical newbie question... But after quite a long period of browsing the internet and this forum I concluded that I need help So I hope that I don't annoy anyone...
My intention is to prepare my Nexus One to use Cyanogenmod. To do that, I want to use a Linux PC instead of a Windows PC. I bought my Nexus from Vodefone in Germany. All current OTAs are installed. Some more specific information: Android 2.2.1, Build FRG83D.
I understood, that at first I have to root my Nexus and need to unlock my boot loader. But I'm a bit confused by the number of different approaches to root/unlock the Nexus One which can be found in this forum and via google. The most of the guides require a Windows PC. To me it was not possible to decide which approach I should follow in order to safely unlock and root my Nexus.
So far I've tried to root my device with the tool "ANDroot", but it won't work... I assume, that I need to follow a more complex approach via a USB-connected PC. I'm a quite experienced Linux (Ubuntu) user and want to use linux for rooting and unlocking my device.
I don't ask for someone to explain to me in detail how to do it! But it would be great if someone cold tell me whether it is easily possible to root and unlock my device from Linux and if so where I might find some comprehensive explanations.
Many thanks in advance and regards from Germany!
try here
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/
Look here, under root: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
I say forget the one-button root and go the OG way, but I guess it just comes down to how comfortable you are with the process.
The process doesn't change very much regardless of what OS you are running.
All of the SDK adb commands are exactly the same - it's just ./adb rather than adb.exe.
Follow the instructions on the Android SDK download page for setting up the SDK on your system, and then follow instructions here for unlocking/rooting/flashing your device.
Just because you use Linux doesn't make you "special"
Thanks a lot for your replies!
Actually I just needed to realize that the Android SDK runs on Linux as well, and that with even less issues than on Win (no need for fancy USB drivers).
Very good for an overall overview: theunlockrDOTcom/2010/01/02/how-to-root-the-nexus-one/
One just has to realize that e.g. "fastboot-windows" has to be replaced by "fastboot_linux"...
A showstopper was the annoying "install-recovery.sh" script which kept me from loading into the new installed recovery image. But after consulting google the following saved me from freaking out:
Code:
./adb shell
$ su
# rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# exit
$ exit
After that is was straightforward to install CyanogenMod by following their specific update guide:
wiki.cyanogenmodDOTcom/index.php?title=Nexus_One:_Full_Update_Guide
And now I'm happily enjoying even a FM radio which I did not expect while thinking of installing CyanogenMod...!
shouldn't adb oem unlock do the trick?
Bloodflame said:
shouldn't adb oem unlock do the trick?
Click to expand...
Click to collapse
It's fastboot oem unlock ... but potato-patato.
To the OP...
I know you probably thought of this already but add
Code:
export PATH=~/android/tools/:$PATH
to your bash .rc script so you don't have to put up with ./adb each time you want to use the adb command.
sassafras
whoops. i should stop posting when tired
don't pay attention to me
Q&A for [TOOLS] Touchpad Toolbox
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I guess I am an idiot because I cannot seem to get 3 downloads that work.
the fat kid said:
i appreciate the quick response, so im throwing in the zip file that says " update-cwm-jcs>>>>>>>>>>>>" along with the "gapps-kk>>>>>>>"
and then unmounting media volume?
again, thank you,.
---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------
edit: just tried all 3 of the recovery files in the op and it still says same error message. any ideas? should i be renaming this from update-cwm blah blah, to the format that it is saying is accepted such as,
It will recognize as a compatible KitKat/DataMedia ROM files that look like:
cm-11-*-tenderloin.zip or
ev_tenderloin-nightly-2014.??.??.zip or
aokp_tenderloin_kitkat_*.zip
again im throwing the gapps-kk-20140105.zip in the ttinstall folder along with the update-cwm-jcs-dm-tenderloin.zip file and then ejecting the tp selecgint unmount media volume and am still getting the error message.
---------- Post added at 03:22 AM ---------- Previous post was at 02:47 AM ----------
geez im a freakin moron.... i had incompatible zip files... sorry folks for the clutter
all other noobs like me WATCH THE VIDEO TWICE.
thanks again, all of you are awesome and hopefully this makes my touchpad relevant again.
Click to expand...
Click to collapse
Would you be so kind as to tell me the 3 downloads you used because I have tried and tried and no success.
Can the Touchpad Toolbox be updated to so that it will accept GAPPS named pa_gapps-*4.4.4-*.zip instead of pa_gapps-*-4.4.2-*.zip?
Either that or remove or allow to skip the requirement that GAPPS zip must be present to do the "Install Android" selection. I eventually worked around it rejecting by renaming the 4.4.4 to 4.4.2 but it will probably frusturate novice users.
tweak42 said:
Can the Touchpad Toolbox be updated to so that it will accept GAPPS named pa_gapps-*4.4.4-*.zip instead of pa_gapps-*-4.4.2-*.zip?
Either that or remove or allow to skip the requirement that GAPPS zip must be present to do the "Install Android" selection. I eventually worked around it rejecting by renaming the 4.4.4 to 4.4.2 but it will probably frusturate novice users.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
TPtoolbox boot menu volume rocker not work.
Hi, I ran the tptoolbox and boots in to menu, but the volume button up or down does work, neither does pressing home. But home and pwer button will reboot device. I tried many times no response from volume rocker in menu. Please help, thanks.
I have the 4G Hp Touchpad 1.5 ghz, dual core 32 gb.
Anyone know if the charging dock will still work following an android installation?
Also, I will search for compatible rom builds, but do themes work as well? (Not sure why they wouldn't, just checking)
sj
Sent from my gTab3 (SM-T210R) on NoleKat v1.4 using [email protected] HD Mobile Pro
sjsharksfan420 said:
Anyone know if the charging dock will still work following an android installation?
Also, I will search for compatible rom builds, but do themes work as well? (Not sure why they wouldn't, just checking)
sj
Sent from my gTab3 (SM-T210R) on NoleKat v1.4 using [email protected] HD Mobile Pro
Click to expand...
Click to collapse
Yes the Touchstone charging dock works on android...
TP Toolbox failed; I'm OS-less; please help
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
I still need help. HELP!
I still need help. Anybody? HELP!!!
vizspace said:
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
Click to expand...
Click to collapse
Have you tried to install it using jcsullins recommendation that you use the Linux way with Mac?
Kit Kat working
OK, like the chap above, I moved the wrong three files into the ttinstall folder. I figured that out. It's the way the thread was written, easy to get confused as they have links right below and say it's those, when in fact it is not (a gapps, recovery and rom need to be moved in there, not the data version of android as that link downloads). Anyway, I sorted it out. Just putting closure on that. Thanks JCSullins! Now we need a Mac version so I need not borrow a friends PC laptop.
vizspace said:
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
Click to expand...
Click to collapse
vizspace said:
--SNIP--
Now we need a Mac version so I need not borrow a friends PC laptop.
Click to expand...
Click to collapse
Have you tried running the script in terminal as jcsullins suggested?
C) Run the script provided with TPToolbox
Extract the contents of the TPToolbox zip file from above.
Navigate to the tptoolbox_v40 directory that was extracted from the zip.
On Windows, run the batch file named tptb_v40_win.bat
On Linux, run the script named tptb_v40_nix.sh
On Mac, try what I said for Linux and let me know what happens.
Click to expand...
Click to collapse
About the .sh file on a Mac; and, question about transferring files
shumash said:
Have you tried running the script in terminal as jcsullins suggested?
Click to expand...
Click to collapse
Hi Shumash, Thank you for writing and being interactive. Yes I did do as suggested and tried running the .sh (linux) file on my Mac. The file opened with TextWrangler and read:
#!/bin/sh
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
TPTB=TPToolbox-2014-05-18-v40.bin
if [ \! -r ${TPTB} ];
then
echo "Cannot find Touchpad Toolbox binary file ${TPTB}"
exit 1
fi
echo "Checking novacom service ..."
novacom -l
rc=$?
if [ $rc -ne 0 ];
then
if [ $rc -eq 1 ];
then
echo "Cannot find novacomd service. Try rebooting or re-installing novacomd"
exit 2
elif [ $rc -eq 127 ];
then
echo "Unable to find novacom program. Try re-installing novacomd"
exit 4
else
echo "Unknown error rc=$rc checking for novacom service. (novacom -l)"
exit 3
fi
fi
echo "Loading TPToolbox ..."
novacom boot mem:// < ${TPTB}
rc=$?
if [ $rc -ne 0 ];
then
if [ $rc -eq 1 ];
then
echo "Cannot connect to Touchpad."
echo "Make sure Touchpad is connected with USB cable."
echo "Make sure Touchpad is in webOS Recovery (bootie) mode."
echo " (where big USB symbol shows on Touchpad screen)"
exit 5
else
echo "Unknown error rc=$rc loading TPToolbox (via novacom boot)."
exit 6
fi
fi
I did a quick search online and found that Macs don't handle the .sh command, rather the command is, believe it or not, .command.
More that that I'm a novice. So I can't say.
And that's when I went to borrow a friend's PC whereupon I double clicked the .win file, extracted it, then ran it in the ensuing window no problem.
--------------------
Now I'm glad someone is reading this thread. I have a question for you (or anyone). Now that I've TP Toolbox'd my HP Touchpad (and I did not select the option to install WebOS on it), how do I transfer files from my Mac (preferred method) to the HP Touchpad now?
I put it in recovery mode (the big USB sign) but it didn't show up on my Mac desktop. It was unrecognized in the Finder too.
So I went back to my friend on hands and knees and am now using TP Toolbox to put an updated file into the ttinstall folder. Is TP Toolbox now the only way to get files on and off my Touchpad? Say it ain't so (and walk me through the process if it ain't so).
There must be an easier way. What am I to do? Please help. Thanks.
vizspace said:
Hi Shumash, Thank you for writing and being interactive. Yes I did do as suggested and tried running the .sh (linux) file on my Mac. The file opened with TextWrangler and read:
--SNIP--
There must be an easier way. What am I to do? Please help. Thanks.
Click to expand...
Click to collapse
From a search on Google (I don't have a Mac):
First in terminal make the script executable by typing:
chmod a+x (yourscriptname)
Then in finder right-click your file and select "Open with" and then "Other...".
Here you select the application you want the file to execute into, in this case it would be Terminal. To be able to select terminal you need to switch from "Recommended Applications" to "All Applications".
NOTE that unless you don't want to associate all files with this extension to be run in terminal you should not have "Always Open With" checked.
After clicking OK you should be able to execute the script by simply double-clicking it.
Click to expand...
Click to collapse
file xfer and mac script
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
vizspace said:
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
Click to expand...
Click to collapse
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
vizspace said:
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
Click to expand...
Click to collapse
This link may be of use to you :
https://www.android.com/filetransfer/.
TP Toolbox on a Mac
This system will not allow me to post my questions. It claims I have a URL in my message (which I do not) and won't allow me to post.
Is there another way to contact you?
Another email? Forum? Etc.?
I saved my questions as I can not submit them here.
There's a problem with the XDA forum.
Mac TPToolbox and other juicy issues
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
Thanks. I followed your link (to google) and read many results. The easiest looking result, which almost worked was this:
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
it was the fourth result, entitled: "How to run a unix shell script from the Mac Finder"
I followed those instructions.
Terminal opened (launched from the Finder window using their noted technique) and here is what was displayed in Terminal: (please note: I exchanged my computer name from it's real name to ABC and XYZ (for this thread; not my real computer name).
Last login: Fri Oct 24 11:27:14 on ttys000
ABC:~ XYZ$ /Users/XYZ/Downloads/HP\ Touchpad\ Tools/tptoolbox_v40/tptb_v40_nix.command ; exit;
Cannot find Touchpad Toolbox binary file TPToolbox-2014-05-18-v40.bin
logout
[Process completed]
I do see the .bin file in the same folder, the TPToolbox folder, as tptb_v40_nix.sh (which, by the way, I duplicated and changed the extension from .sh to .command, prior to searching in Finder as outlined in above links' description).
So I don't know what to do.
I know a lot of things you likely do not know; but you clearly know more about computers than I. Please be patient and explain succinctly.
I tried your method, first replied from , with and without brackets, that didn't help.
--------------------------------------------------------------
Regarding Android File Transfer, and I thank the contributor below for chiming in with that advice, I've used that, but it only works sometimes. It is not reliable; and doesn't see ALL the files (as a WebOS USB connection to my Mac used to).
Is there some way to put the HP Touchpad into USB mode and connect it to my Mac (like I used to before on the HP WebOS side (when I had an HP WebOS side)? This may be argument enough to keep the WebOS side. (I can put it in USB mode on Android, but the Mac does not recognize the HP Touchpad at all doing it that way).
---------------------------------------------------------------
Another unrelated question: What ever happened to PreWare? I can't find it anywhere. I installed Jason Robitaille's WebOS QuickInstall 4.5.0 and ran it ok. But when one clicks on the globe, there's no Preware. When one clicks on the Search field , there are zero results (except themes). No Applications, Kernels, Patches, etc.. Nothing. So what ever happened to Preware?
Not having been able to find that, and with Palm no longer supporting WebOS at all after Jan 15, 2015, was the nail in the coffin for WebOS for me. If I can't find Preware and all the apps and tweaks that come along with it, the only reason I can see keeping any WebOS on this tablet at all is to be able to put it in to WebOS USB mode and easily connect it to my Mac.
-----------------------------------------------------------
Lastly, I'm running JCSullins build titled/dated: cm-11-20141002-SNAPSHOT-jcsullins-tenderloin.zip
How do I take a screenshot with this ROM? It used to be Power button and lower volume button, but that screenshot option is no longer available in this JCSullins build, nor in the previous build: cm-11-20140625-SNAPSHOT-jcsullins-tenderloin.zip
Any ideas how to take a screenshot?
---------- Post added at 02:59 PM ---------- Previous post was at 02:43 PM ----------
sstar said:
This link may be of use to you :
https://www.android.com/filetransfer/.
Click to expand...
Click to collapse
Regarding Android File Transfer, and I thank the contributor below for chiming in with that advice, I've used that, but it only works sometimes. It is not reliable; and doesn't see ALL the files (as a WebOS USB connection to my Mac used to).
Is there some way to put the HP Touchpad into USB mode and connect it to my Mac (like I used to before on the HP WebOS side (when I had an HP WebOS side)? This may be argument enough to keep the WebOS side. (I can put it in USB mode on Android, but the Mac does not recognize the HP Touchpad at all doing it that way).
---------------------------------------------------------------
Another unrelated question: What ever happened to PreWare? I can't find it anywhere. I installed Jason Robitaille's WebOS QuickInstall 4.5.0 and ran it ok. But when one clicks on the globe, there's no Preware. When one clicks on the Search field , there are zero results (except themes). No Applications, Kernels, Patches, etc.. Nothing. So what ever happened to Preware?
Not having been able to find that, and with Palm no longer supporting WebOS at all after Jan 15, 2015, was the nail in the coffin for WebOS for me. If I can't find Preware and all the apps and tweaks that come along with it, the only reason I can see keeping any WebOS on this tablet at all is to be able to put it in to WebOS USB mode and easily connect it to my Mac.
vizspace said:
--SNIP--
Last login: Fri Oct 24 11:27:14 on ttys000
ABC:~ XYZ$ /Users/XYZ/Downloads/HP\ Touchpad\ Tools/tptoolbox_v40/tptb_v40_nix.command ; exit;
Cannot find Touchpad Toolbox binary file TPToolbox-2014-05-18-v40.bin
logout
[Process completed]
I do see the .bin file in the same folder, the TPToolbox folder, as tptb_v40_nix.sh (which, by the way, I duplicated and changed the extension from .sh to .command, prior to searching in Finder as outlined in above links' description).
So I don't know what to do.
--SNIP--]
.
Click to expand...
Click to collapse
My guess is that executing the shell script by double-clicking starts it in the wrong directory. Open a terminal in the directory where you have the Toolbox files and execute it from the command line there.
In case anybody cares, here's a pure C reimplementation of 'cuber.py'
(my own earlier reimplementation of @vortox's signature.py).
This is what I'm using in my '1-Click' bootloader unlock VM...
See 'grep ^gcc' for "build instructions".
Hack, you can probably build this for ARM and run it right on your very HDX tablet... (-;
UPDATE (JanuaryFebruary 2017):
OK; so, @zivimo had built this for ARM, but people still haven't noticed.
I repacked his binary from a .tar.gz to a .zip archive and decided to spell out the instructions for use.
Perhaps, this helps... With the right bootloader in place, and adb/fastboot installed (and working),
the unlock is as easy as follows...
Download and extract unlock.zip (SHA256: e40e3010f8eccfa9cbd1e73eecac30cf799099d183de23b2d256fc3407f143f6e5db0b8d82c8fd2a25a22b0a598014d22a2ec33cef27a8d4b65a36acde08f27a)
to the same directory that holds the adb and fastboot executables (unless you have added them to your PATH)
Click on get_code.bat in the extracted folder
-- optional (but commonly required) step(s) --
fix root (roll back, if you need to), flash vulnerable bootloader
[you'll definitely need to perform at least some of these if the last step fails]
Click on unlock.bat in the extracted folder
The archive also includes .sh variants of the .bat files for convenience.
You could also just click to show the hidden section and cut&paste... (-;
Code:
[STRIKE]unzip cuber.zip[/STRIKE]
adb push cuber /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/cuber
adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'
adb pull /sdcard/unlock.code
adb shell rm /sdcard/unlock.code /data/local/tmp/cuber
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.code
NOTE: download and extract the attached 'cuberunlock.zip' and run the above commands
in the directory where 'cuber' got extracted to.
Nice job! Originally I wanted to use OpenSSL BigNum too, but I hadn't enough time and Python was easier to use
hey,
made a static compile with an arm debian (jessie). seemed the easiest solution to me. compile command:
Code:
# gcc -fPIE -static cuber.c -o cuber -lssl -lcrypto
# strip cuber
# ldd cuber
not a dynamic executable
# ./cuber
Usage: cuber [RSA-bytes] < data > sig
seems to work. arm(!) binary attached.
ok draxie, you pointed me here but something seems to be missing. i downloaded unlock.zip, put the files in my adb directory. when i run get_code.bat, it pushes cuber to the kindle in the right directory, changes permissions (dont see any errors there) but then stops saying the system can't find the specified path. Whats funny is i used es file explorer to check the paths in the script, and they are there so not sure where the hang up is.
chin_bone said:
ok draxie, you pointed me here but something seems to be missing. i downloaded unlock.zip, put the files in my adb directory. when i run get_code.bat, it pushes cuber to the kindle in the right directory, changes permissions (dont see any errors there) but then stops saying the system can't find the specified path. Whats funny is i used es file explorer to check the paths in the script, and they are there so not sure where the hang up is.
Click to expand...
Click to collapse
Did you check all three paths?
/data/local/tmp
/sdcard
/sys/class/block/mmcblk0
The 2nd one _may_ be problematic if you're on SafeStrap.
I don't know why. I'm yet to install that on one of my test
devices to investigate. (Or, was that the 1st... )
The 0 in the 3rd one may actually be a 1 on some systems.
I have a few extra lines in my VM script to work around
that, I can easily add that here as well, if that turns out
to be the issue.
BUT, to try and troubleshoot: how far does the script get?
If it didn't complain with the permissions, the 1st path is probably OK.
Does it print your manfid/serial?
If so, mmcblkX would be right as well.
Any chance that you're on SafeStrap?
Can you push/pull to/from /sdcard?
- - - - -
On a second thought: I've only ever tested this on Linux.
String quoting on Windows may work differently, and could *royally* mess up how that more complex command is interpreted.
I'll test tomorrow; it's like 20 past 1am here. I need to get some sleep.
In the meantime, as a workaround, you could just hard-code your manfid/serial, and replace this line:
Code:
adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'
by the decidedly much simpler:
Code:
adb shell 'echo 0xmmssssssss | /data/local/tmp/cuber > /sdcard/unlock.code'
draxie said:
Did you check all three paths?
/data/local/tmp
/sdcard
/sys/class/block/mmcblk0
The 2nd one _may_ be problematic if you're on SafeStrap.
I don't know why. I'm yet to install that on one of my test
devices to investigate. (Or, was that the 1st... )
The 0 in the 3rd one may actually be a 1 on some systems.
I have a few extra lines in my VM script to work around
that, I can easily add that here as well, if that turns out
to be the issue.
BUT, to try and troubleshoot: how far does the script get?
If it didn't complain with the permissions, the 1st path is probably OK.
Does it print your manfid/serial?
If so, mmcblkX would be right as well.
Any chance that you're on SafeStrap?
Can you push/pull to/from /sdcard?
- - - - -
On a second thought: I've only ever tested this on Linux.
String quoting on Windows may work differently, and could *royally* mess up how that more complex command is interpreted.
I'll test tomorrow; it's like 20 past 1am here. I need to get some sleep.
Click to expand...
Click to collapse
It's all good draxie, i figured out what i was doing wrong with the other procedure, that damn STEP 2, once i did it, everything fell into place. Bootloader unlocked and now just trying to figure out which rom to try first. Thanks again, you guys are great and i know how valuable everyones time is. :good:
I keep hitting road blocks, I am rooted and on Fire OS 4.5.5.2 I click get code a screen flashes up then I click Unlock and my Kindle boots to the Grey Kindle screen with Fastboot underneath and nothing else happens. Same happens when I copy and past the code into ADB. What step am I failing at? Thanks for the help!
pdanforth said:
I keep hitting road blocks, I am rooted and on Fire OS 4.5.5.2 I click get code a screen flashes up then I click Unlock and my Kindle boots to the Grey Kindle screen with Fastboot underneath and nothing else happens. Same happens when I copy and past the code into ADB. What step am I failing at? Thanks for the help!
Click to expand...
Click to collapse
@draxie - I have no experience with this tool; python/gmpy2 works reliably for me. Sorry to pull you in ...
Davey126 said:
@draxie - I have no experience with this tool; python/gmpy2 works reliably for me. Sorry to pull you in ...
Click to expand...
Click to collapse
I am up and running now, unlocked and running kk-fire-nexus-rom-thor-20161017. Play store is also up and running.
pdanforth said:
I am up and running now, unlocked and running kk-fire-nexus-rom-thor-20161017. Play store is also up and running.
Click to expand...
Click to collapse
Did you end up using some other method, or did these scripts work for you in the end?
Either way, others may find useful if you could share whatever worked for you. (-;
Unfortunately, I still haven't had a chance to test these scripts in Windows;
so, I couldn't answer your first call for help in a good way. If there's something
wrong and there's enough interest, I'll be happy to fix it as soon as I can.
draxie said:
Did you end up using some other method, or did these scripts work for you in the end?
Either way, others may find useful if you could share whatever worked for you. (-;
Unfortunately, I still haven't had a chance to test these scripts in Windows;
so, I couldn't answer your first call for help in a good way. If there's something
wrong and there's enough interest, I'll be happy to fix it as soon as I can.
Click to expand...
Click to collapse
@stangri did my unlock file and I used this thread to unlock https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had trouble making the Unlock file, once that was done and some help from other users I am now up and running!