Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Quick update, I have Cyanogen 6.0.0 working on the phone now..
But i'd still like to be able to restore!
jamin100 said:
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Click to expand...
Click to collapse
I would suggest trying to type the directory instead of using default. When the restore prompts you to either type the directory or hit enter... instead of hitting enter type:
/sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
See if it gives you the same error.
NOTE: That IS case sensitive.
Thanks for your reply, unfortunately it does give the same error, I have 3 nandroid backups but cant restore any of them which is worrying incase anything happens to the phone!
Please help
Try this... while in the shell... type the following:
Code:
ls -l /sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
It should bring up a list of 5 files. Go ahead and attach a screen if you can if you are getting a list of files. If not let me know what error you get.
Thanks for your help,
here's the screen shot
Nobody encountered this problem?
Ok... sorry had you look in the wrong place. I thought it was looking in the directory with the image in it for what it needed. I just looked at the nandroid code. Turns out... it looks for some executables that are required for the script to run. It doesn't have to do with your image and I think your images are probably fine.
I need you to run 2 more commands so I can see where the problem is. First run:
Code:
env
Next run:
Code:
which unyaffs
The "env" command should show your enviroment variables. What we are looking for is for /system/bin to be in your "PATH" variable. It should be because it checks for another executable first "flash_image" and it is not coming up with an error. The second file it is checking for is "unyaffs". Next you need to check and make sure unyaffs is actually in your /system/bin folder. It is probably not... and would explain the error you are getting.
I guess my first question is... is this happening on all ROMs you have tried (or have you only gotten one up and running)? If it is there may have been a problem when you flashed it. Even though it is possible that you could copy it to the /system/bin I would suggest not doing this. The reason is because if that one file is missing... there may be other files missing that should be there from when you flashed your ROM. These missing files... if there are any... could cause problems later. It might be best just to reflash whatever ROM you are using. I would suggest CM6 (not nighties) and then moving to some other ROM once you get a "known good" to work with.
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
jamin100 said:
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
Click to expand...
Click to collapse
Hmmm... the permission denied is normal. That is because it is a folder and not an executable. You should be able to do:
Code:
ls -l /system/bin
This will list what is in your /system/bin directory. As for your path being different... that seems a bit strange. I am doing the commands from a terminal on my device... once I get back home today I will do it through the ADB shell and see what I get. The "which" command will only look in the folders in your "PATH" variable for the executable. If /system/bin is not in there I am not sure how it is passing the part where it looks for "flash_image". In my sbin folder I only have the ADB daemon (adbd) executable. What you could do is manually add the /system/bin to your PATH variable while in the shell... that may work. You can try the following:
Code:
PATH=$PATH:/system/bin
Run that before running your restore command. That should manually place the directory you need into your PATH environment variable. I will do a little testing with ADB once I get home and update this if I get to before you try it.
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
jamin100 said:
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I checked my environment variables via ADB. Mine did show the /system/bin in my PATH variable. Seeing as this is a shell being run on your device... I would still venture to say that something may have went wrong when you flashed your ROM originally. That or something you installed changed it for some crazy reason (and shouldn't have). Either way, I still think it would be best to flash again... possibly to a different version. I know you would have had to get a modified version of CM6 so... if you don't mind me asking where did you get your copy?
EDIT: Correction... I am getting the same path variable as you when in recovery mode. I am not quite sure why this is... the guide I found for using nandroid restore through ADB doesn't seem to run into this issue. It might be some kind of issue related to just Amon_Ra recovery. This would mean that Amon_Ra Recovery just didn't add it to the PATH variable... which I guess is rather odd... but whatever. Just try manually adding it to the PATH variable as mentioned above and then run the restore. It should work then.
EDIT 2: I did a bit of researching on that error you are getting when you try and restore in recovery. Reference:
http://forum.xda-developers.com/showthread.php?t=621940
Various people point to things that may cause this error. Is your phone charged? Do you have plenty of space on your SD card?
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
consider this thread deprecated, will keep the original post here for historic sake, and maybe it will help someone down the road
there are way easier ways to do this now
please do not try any of this
if you do decide to do anything on this thread, it is at your own risk
you have been warned
Code:
get:
[url]http://www.droidaftermarket.com/koush//test/inc.zip[/url]
[url]http://www.droidaftermarket.com/koush//test/keys[/url]
1. Boot to recovery with adb (if u dont know how...learn)
2. Run the unrEVOked method to get an adb shell, then do su to get # (if u dont know how...learn)
3. push the inc.zip to /sdcard/update.zip
4. push the keys file to /sdcard/keys
5. Do:
/system/bin/mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
/system/bin/rm /res/keys
/system/bin/cat /sdcard/keys > /res/keys
/system/bin/ps recovery // note the pid of it
/system/bin/kill <pid>
6. Vol+ and Power to get menu again
7. Vol - then power to run the update.zip
8. Profit!
Big thanks to the unrEVOked team and koush for making this happen!
This method does not stick, it is only good until reboot, but adb works now so have fun
Some problems with accessing /data and some other stuf, but well get it sorted out
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
WOW
Worked like a charm
Video Tut
http://www.youtube.com/watch?v=BuPFee7IIfM
test key
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
B-dub25 said:
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
Click to expand...
Click to collapse
right click on the link and hit save as, remove the .txt extension once it downloads. Look at my video which i have a link for one post above if you need help.
thanks
thanks i`ve been doing three things at once lol got conf. i had to make a program for my finiles c++ programming fun and linux adm. finile too thanks thou
ejlax said:
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
Click to expand...
Click to collapse
You need to go through the rooting process again, since we can't flash recovery yet, for anyone that was wondering. At least up until the point where you inject the payload.
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
I can get adb to work just about everytime
I can even get recovery to update but still it wont stick no matter what I try. So needless to say anytime I want to try anything I must do the entire procedure over again
There has to be a better way or is this all caused but the nand protection many talk about. Sorry im kindof of newbie to this sort of problem.
All other phones I have rooted for friends usually take once you get it to work. Mytouch 3g fender, a bunch of Moto droids and one N1 so far, and of course my DI
I hope someone figures this out soon then we may start seeing some ROMS, I cant wait for a vanilla rom that I can dress up the way I want and not have all the bloat from SenceUI. Ony thing i'd like to keep would have been htc's weather widget and maybe freindstrean. If I can use it with Sweeter home preview 2. Im so happy with this last release of SH2 its rock solid on my incredible like its been on the moto droid the last 2 or 3 releases for me.
ihtfp69 said:
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
Click to expand...
Click to collapse
Thats basically the hurdle everyone is trying to jump right now. getting a valid nand backup that works, once that is done, custom recovery and roms will be flowing. Im also working on some messing around to try to help out, but on the same hand being careful not to brick since theres no way to restore at this time.
Has anyone heard how progress of making sp recovery stick going? Thanks.
tats_06 said:
Has anyone heard how progress of making sp recovery stick going? Thanks.
Click to expand...
Click to collapse
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
760hacker said:
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
Click to expand...
Click to collapse
Thanks!!! Thats reassuring.
Can anyone please post a copy of the keys file? The link is down and I can't find it anywhere else either!
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
hockeyfamily737 said:
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
Click to expand...
Click to collapse
Just download a file manager, (es fileexplorer, or root explorer) and install it that way. or if you have adb and all the drivers you need for it.
Put the .apk in the tools folder in the SDK
and go to it in a command prompt and type adb install titaniumbackup.apk..
Or whatever you apk is named.
if you need help, dont quote this, just send me a pm for help =]
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
kyouko said:
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
davidevan said:
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
Click to expand...
Click to collapse
Yea they are. Besides, personally I'd do it the way you mentioned; either first using a filemanager (easiest imo) or via adb install
Only reason I replied was in case there was a specific reason he'd only want to use terminal emulator and not adb or a FileMan
Edit: Oh I see what I think you're referring to, the line:
Adb commands are completely different than terminal commands.
Click to expand...
Click to collapse
That was just directly copied from a post I made before something about wanting to "adb push" with TE, it had nothing to do with your response
Sent from my Android using Tapatalk
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
btw click my thanks meter ;]
its the ony thing i have left lmao! :'(
davidevan said:
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
Click to expand...
Click to collapse
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
davidevan said:
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
Click to expand...
Click to collapse
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
hockeyfamily737 said:
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
Click to expand...
Click to collapse
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
waffle_ said:
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
Click to expand...
Click to collapse
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
"
hockeyfamily737 said:
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
Click to expand...
Click to collapse
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
laie1472 said:
"
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
Sitll no good installing ADB at work, but I did get a good ADB workout at home this weekend rooting my son's Optimus......Wholy crap!!! Revert to old software, lose the lcd display, root with rage against the cage, push recovery to the phone, revert back to current version of software, lose root, and then re-root on current software with recovery already installed, what a process that was!!!! BTW.... Terminal Emulator commands worked perfect. Mistake I was making was trying to "push" from my SD card instead of "copy".
So iam running bo 2.0.1 with cwm 5.5.0.4. Tried to update to cwm 6 touch by replacing cwm image in pretty much all the aio's.. it'll either say it pushed and still reboot into old cwm or I'll get permission denied on /data/local/temp/sh and mmcblk14 even after giving them all read write and execute permission. Can someone help me get this on my revo? Maybe a guide to do it with adb? It would be much appreciated..... sorry if this is posted in wrong section... I wasn't sure where it would be seen by the dev 's who can help
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
slimzim said:
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
Click to expand...
Click to collapse
The same exact way I've done it. Numerous times with no success. It said it pushed but reboot back into 5.5.0.4
Anyone else have this problem? How can I achieve this with adb or file explorer... the method posted just isn't pushing the image...
To do it from within the phone... (Insert the usual disclaimers here about messing your phone up here. It's all you from here on out)
You can open up the .bat batch file of one of the rooting tools that have CWM install scripting.
Copy the commands they perform in preparation for the procedure. Remove adb shell and push from the commands as you will be doing this from inside the phone, not via adb. I think you might have to remove some open/close quotation marks too, unnecessary from the terminal prompt.
Rename the new CWM file to match the command prompt change the command to match the new CWM filename.
Move that file to the expected location (/local/tmp if I recall correctly).
Use app Terminal Emulator to create a terminal windows and type su and Press enter. That will get superuser access.
Then, issue the commands you took note of from the batch file.
Reboot to Recovery to test if successful.
I used this basic process to get CWM on after rooting stock ZV9 a few weeks ago. Combing through a couple different batch scripts, I wanted to make sure I wasn't going to bork my phone. The adb remount command doesn't seem to work after rooting for some reason. That seems to be the cause of adb failure to update CWM.
If you get into trouble, I can't help you much there as I'm not that advanced. Good luck.
Anyone else with tips please chime in and help the chap :beer:
Sent from my VS910 4G using Tapatalk 2
Ill try it out. Thanks for the advice
Didnt work.. iam hoping that resetting back to stock and using that image from the start will work
Weird. I was expecting to hear good news since that's how I got CWM onto my phone. Good job trying!
Sent from my Transformer Prime TF201 using Tapatalk 2
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!