Related
I get the:
E: No Signature
E: Verification Failed
Installation aborted
no matter what update I try to apply. (I am also hung up on the G1 screen when I try to regular boot, so right now I am pretty stuck). When I home+power it also goes to the old triangle exclamation point screen rather than the cyanogen recovery (which I just installed). Any thoughts would be appreciated. I am stuck.
Hey, did you have any response to your problem? I am having the same problem with my spl update zip file, it aborts every time. Cheers
i also have this problem
Does anyone have a solution?
just did this
yea just go to the market download telnet
(go to the front of you screen press enter then type telnetd and press enter again so it could open) then
Type the following into Telnet (these commands will give you root access easier in the future):
# # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# # cd sdcard
# # flash_image recovery recovery.img
# # cat recovery.img > /system/recovery.img
(have a recovery image as well on you sd card)
Stuck Too !!
Sounds like I'm stuck at the G1 boot screen too, also trying too update to new hard spl after updated radio. I'm not able to get to telnet because stuck at G1 screen. I used the original root on Wiki and the recovey never took. But the Android recovery was working and letting me have root and apply updates. I was trying to flash a dRizzle hero. Directions had me update radio and spl using the link from his page it took me to haykuro's sapphire htc dream page where i did what it said, flash radio first (that took) then hardslp.
It never took and stuck at G1. Could it have something to do with the fact that i was doing this all from the downgrade rc29? Any help would great.
youngrony said:
yea just go to the market download telnet
(go to the front of you screen press enter then type telnetd and press enter again so it could open) then
Type the following into Telnet (these commands will give you root access easier in the future):
# # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# # cd sdcard
# # flash_image recovery recovery.img
# # cat recovery.img > /system/recovery.img
(have a recovery image as well on you sd card)
Click to expand...
Click to collapse
When i try "(go to the front of you screen press enter then type telnetd and press enter again so it could open)" this does not work...do you no why? Thanks!
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
mobilehavoc said:
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
Click to expand...
Click to collapse
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
chuckhriczko said:
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
Click to expand...
Click to collapse
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
mobilehavoc said:
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
Click to expand...
Click to collapse
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
chuckhriczko said:
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
Click to expand...
Click to collapse
What he said...but yes, at the steps you quoted, mobilehavoc, you are capable of root access (you don't actually have it until you run that "su" command ). That allows you to read and modify otherwise locked away files and tweak to your hearts content!
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Grinder16 said:
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Click to expand...
Click to collapse
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
thecodemonk said:
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
Click to expand...
Click to collapse
Dont see that folder - I guess that is not good. Any ideas?
Grinder16 said:
Dont see that folder - I guess that is not good. Any ideas?
Click to expand...
Click to collapse
You must do a backup BEFORE you can do a restore..
To clarify for everyone, here's a breakdown of the steps:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
This copies the asroot2 program to the /data/local folder on your phone.
adb shell
This logs you into the phone. From here on out, you are no longer executing Windows commands from a DOS shell - you are actually executing Linux commands on the phone.
chmod 0755 /data/local/asroot2
This changes the permissions on the asroot2 program so that it can be executed.
/data/local/asroot2 /system/bin/sh
This actually runs the root exploit and creates a file called /system/bin/sh that we will later turn into su.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This unmounts the /system partition and remounts it as writeable.
cd /system/bin
This puts you into the /system/bin folder.
cat sh > su
This creates the su program.
chmod 4755 su
This changes the persmissions on the su file to allow it to be executed.
theresthatguy said:
You must do a backup BEFORE you can do a restore..
Click to expand...
Click to collapse
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Grinder16 said:
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Click to expand...
Click to collapse
Boot to the recovery image then select "nandroid backup"
jonnythan said:
Boot to the recovery image then select "nandroid backup"
Click to expand...
Click to collapse
Can you provide those steps? Sorry but complete newbie here
"I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error"
Go there but select Backup instead of Restore.
Turn the phone off, hold the Home key, and turn it on. When you get to the screen with the green text select nandroid backup.
For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)
so this takes out the HBoot? and goes straight to Recovery Rom?
unfortunately no,
but it lets you skip the step "Vol up+power" and go straight to stock recovery.
From there you can use the "fake-flash"
awesome...Thanks for sharing, i will try this
I would recommend "rm /system/bin/reboot" before pushing the new one.
Great job! Works like a charm!
I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978
wcasdf said:
For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)
Click to expand...
Click to collapse
C:\Documents and Settings\Owner>adb shell
# mount /dev/block/mtdblock4 /system
mount /dev/block/mtdblock4 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# exit
what am i doing wrong??
worked great, we are only one step away now
Help......
Hi Sorry to bother..
Have started the process got to push the file to the system bin. However when then attempting the next command adb shell, i recieve the following error:-
- exec '/system/bin/sh' failed: Not a directory (20) -
Any advice????
Cheers
Andy
.....Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?
Sorted....
Kali- said:
wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?
Click to expand...
Click to collapse
Absolutely right Kali........the mtdblock3 resolved the issue.....now able to enter recovery mode and also back up rom.....
Brilliant....many thanks......
watzone69 said:
I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978
Click to expand...
Click to collapse
I was just afraid the thread would get moved with these super-strict mods in this board.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Worked great. Now the reboot commands in ROM Manager and Quick Boot work.
tells me reboot file is not there its in the androidsdk\tools folder
Sporkman said:
tells me reboot file is not there its in the androidsdk\tools folder
Click to expand...
Click to collapse
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...
joeykrim said:
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...
Click to expand...
Click to collapse
i dropped the file in C:\androidsdk\tools WHERE it needs to be
trying to figure this for my desire i understand block needs to be 3 and the rest the same but
keep getting device or resource busy when trying the mount command?
fixed it..you need to be in recovery before doing the above-otherwise you get a resource busy message
dont forget to change to block3 not 4 if using desire- rom manger now works as it should !! thanks
joeykrim said:
...OP: where did this reboot binary come from?
Click to expand...
Click to collapse
I'm not the OP but I originally got mine from the Hero sub-forum:
http://forum.xda-developers.com/showpost.php?p=5356050&postcount=623
I need some help please, my phone wont boot and is stuck at the M logo. I am using dexters ROM with its patch. I wanted to change the android font from the standard droidsans to the Ubuntu font. I downloaded the ttf's from the ubuntu website and started looking on how to go about it.
So after searching the internet, I saw most people were doing it using adb push to replace the fonts in the /system folder. First problem that I encountered was adb not working, but after updating my $PATH to add platform tools it started working. After that when I tried the push command it said the /system was read only. I followed these instructons to make the /system folder read/write.
adb shell
$ su
# mount
# # mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system
After this I did:
mv /system/fonts/DroidSans.ttf /system/fonts/DroidSans_org.ttf
# exit
$ exit
I tried to adb push the fonts but they permission was denied. I them removed the original fonts and thats when the screen went black. I did adb reboot and now the phone wont go past the M logo. Went into normal recovery using the camera, media and power keys. Did a factory reset. Still stuck. I have no idea wtf I did, I just usually follow instructions and everything is fine dunno what happened this time. I dont know how to go back into open recovery and flash the rom again. Any help would be appretiated. Thanks!
You should be able to get into openrecovery by pressing and holding the volume up key while powering on.
Thank you! It worked now to get around to fixing this Thanks again
Hi,
I have followed all of these steps theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/[/url] up to VI. Stop the Phone from Uninstalling the Custom Recovery Image. After I shutdown the phone I hold the volume up and press the power to go into fastboot however when I press recovery, the clockworkmod does not save and just boots the stock recovery. Once I type in adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh I get mount: Operation not permitted.
I hope someone can help me. Thanks to whoever is reading this.
shuandroid said:
Hi,
I have followed all of these steps theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/[/url] up to VI. Stop the Phone from Uninstalling the Custom Recovery Image. After I shutdown the phone I hold the volume up and press the power to go into fastboot however when I press recovery, the clockworkmod does not save and just boots the stock recovery. Once I type in adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh I get mount: Operation not permitted.
I hope someone can help me. Thanks to whoever is reading this.
Click to expand...
Click to collapse
the correct way to flash the recovery would be through fastboot. "flashing" it with rom manager doesnt cut it. do a search, theres lots of info here. good luck
I think he already flashed CWM with fastboot, and is now trying to rename install-recovery.sh
Just follow these steps:
1) Boot up your phone.
2) Use Root Explorer to browse to /system/etc
3) Press the "Mount R/W" button
4) Long press on install-recovery.sh
5) Rename it to "install-recovery.sh.bak"
6) Go back into bootloader
7) Use fastboot to flash ClockworkMod Recovery again like you did the first time.
shuandroid said:
Hi,
I have followed all of these steps theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/[/url] up to VI. Stop the Phone from Uninstalling the Custom Recovery Image. After I shutdown the phone I hold the volume up and press the power to go into fastboot however when I press recovery, the clockworkmod does not save and just boots the stock recovery. Once I type in adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh I get mount: Operation not permitted.
I hope someone can help me. Thanks to whoever is reading this.
Click to expand...
Click to collapse
mount requires root permissions. Are you su?
Sent from my Nexus S using XDA Premium App
krohnjw said:
mount requires root permissions. Are you su?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Does adb have inherent su privs? Or is the problem that he did not request su privs?
matt2053 said:
Does adb have inherent su privs? Or is the problem that he did not request su privs?
Click to expand...
Click to collapse
adb does not have any inherent root privileges. You either need an insecure boot image for adb remount or you need to request su privileges and remount /system manually (or through an app like Root Explorer).
matt2053 said:
I think he already flashed CWM with fastboot, and is now trying to rename install-recovery.sh
Just follow these steps:
1) Boot up your phone.
2) Use Root Explorer to browse to /system/etc
3) Press the "Mount R/W" button
4) Long press on install-recovery.sh
5) Rename it to "install-recovery.sh.bak"
6) Go back into bootloader
7) Use fastboot to flash ClockworkMod Recovery again like you did the first time.
Click to expand...
Click to collapse
Thanks, worked like a charm! I dunno how you knew to do that, but thank you!
Jyro275 said:
Thanks, worked like a charm! I dunno how you knew to do that, but thank you!
Click to expand...
Click to collapse
He new that because this was asked many times.
Thank you so much. It worked for me too.
Sent from my Nexus S 4G using XDA Premium App
matt2053 said:
I think he already flashed CWM with fastboot, and is now trying to rename install-recovery.sh
Just follow these steps:
1) Boot up your phone.
2) Use Root Explorer to browse to /system/etc
3) Press the "Mount R/W" button
4) Long press on install-recovery.sh
5) Rename it to "install-recovery.sh.bak"
6) Go back into bootloader
7) Use fastboot to flash ClockworkMod Recovery again like you did the first time.
Click to expand...
Click to collapse
Thanks, dude. It works like charm for me, too.
Seems i do not have that script :/
Code:
[email protected]:/system/etc # ls
NOTICE.html.gz
apns-conf.xml
audio_effects.conf
bluetooth
contributors.css
dbus.conf
dhcpcd
event-log-tags
fallback_fonts.xml
gps.conf
hosts
init.goldfish.sh
media_profiles.xml
mkshrc
permissions
ppp
resolv.conf
secomxregistry
security
sysctl.conf
system_fonts.xml
updatecmds
vold.fstab
wifi
any clue?
need help, already install superuser on my nexus s slcd, but does go into recovery. tried the rootexplorer method also, please help. nexus s 2.3.6 i9023.