Moved to proper forums Sorry for mistake
it is always better to unroot ur tab before updating via OTA ........just Google it and see the method how to unroot .........
CHEERS
HIT THANKS BUTTON IF I HAVE HELPED
steddyeddie said:
Hey all, new to the site and needing some advice please.
I got a Gal tab 2 10.1 and my mate said i should root it and pointed me to the How To] ROOT- Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110 & 4.0.4 UPGRADE or OEM] post,
i followed it to the letter and was able to root my tab, "i still have no clue what i just did" anyways i few days ago i got a firmware update pop up and the tab so i tried to install it now its saying Signature verification Failed and update aborted.
anyone can advise me and what i need to do please. i cant reply to posts on the Root - galaxy tab 2 10.1 post so am asking here.
Thanks in advance. Ed
Click to expand...
Click to collapse
Or.......go to the Galaxy tab 2 forum
Different cpu, different tablet, hence different sections on XDA
Sent from my GT-P7510 using Tapatalk 2
jmitr said:
Or.......go to the Galaxy tab 2 forum
Different cpu, different tablet, hence different sections on XDA
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Tried to unroot it from the dev post, notting happening still saying failed. here is what comes up when i try installing the new update
CWM- Based recovery v 5.5.0.4
E:invalid command argument
Finding update package
Opening update package
Verifying update package
E:failed to verify whole file signature
E:signature verification failed installation aborted
steddyeddie said:
Tried to unroot it from the dev post, notting happening still saying failed. here is what comes up when i try installing the new update
CWM- Based recovery v 5.5.0.4
E:invalid command argument
Finding update package
Opening update package
Verifying update package
E:failed to verify whole file signature
E:signature verification failed installation aborted
Click to expand...
Click to collapse
I would be tempted to manually unroot the phone.
pc$ = shell on your computer
android$ = non-root shell on your phone
android# = root shell on your phone
Code:
# make sure phone is connected
pc$ adb devices
# backup su and Superuser.apk
pc$ cd my_backup_dir
pc$ adb pull /system/bin/su
pc$ adb pull /system/app/Superuser.apk
# remove su and Superuser.apk from phone
pc$ adb shell
android$ su
android# mount -o remount,rw /system
android# rm /system/bin/su /system/app/Superuser.apk
android# mount -o remount,ro /system
android# exit
android$ exit
pc$
If you have installed busybox, it can be backed up and deleted in much the same way.
Related
Testman08
Junior Member Join Date: Apr 2010
Posts: 1
I am having trouble with installation instructions from Walkthru setups hxxp://forum.xda-developers.com/showthread.php?t=647707. I have installed the rooted img and it shows i'm running 2.1 (original software was unrooted 1.5) but when I attempted to go to step three of custom recovery "Open up a command prompt and go to your tools directory, and execute these commands:" i am having a hard time not getting errors when I attempt to enter these:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
the question I have is how do you go from command prompt to tools directory? what path is it following instructions from above thread? can I use this "all in one script" even though I am already rooted?
firmware 2.1, baseband 2.40.00.01.22, kernel 2.6.29-5898f66b, software 2.19.605.1 and shows test keys. Currently I keep getting force close on maps and navigation apps.
Thanks in advance for any assistance.
Got it resolved......
How did you get it resolved ???????
Im so stuck
Ki1lACrAcK said:
How did you get it resolved ???????
Im so stuck
Click to expand...
Click to collapse
droidfreak said:
have you made it to the tools directory? if you actually go to the tools file on your computer, on the address bar you will see what you need to type.... either (red font)
cd C:\AndroidSDK\tools
that was after I moved the tools folder otherwise it was:
cd C:\AndroidSDK\android-sdk-windows\tools
type one or the other exactly how I have it up top....cd and all....
Click to expand...
Click to collapse
option in bold worked for me
Now if i can figure out how to get the custom rom installed lol
Hmm Im having a similar issue but
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Okay, I seriously had enough of people saying is this AmonRa or whatsoever. I Derived both files from here and decided to make those instructions/script easier for you to understand. This recovery covers most basic needs (wipe,backup,restore,flash etc.) , so if you are going to keep complaining about my thread title/contents, I'll be glad to remove this thread and leave you people to figure out how to install custom recovery
WARNING : Only for P500....
Many people tried installing custom recovery, but ended up hard resetting your phone wondering WTF went wrong right? Like you people I ended up resetting 4 times =.=ll so..now I've succeeded, I'm just gonna share how its done!
==============================================================
Files Needed :
recovery-RA-thunderg-2.2.1-GNM.img.zip
flash_image.zip
(Both downloadable from below)
==============================================================
The files preparation process:
1)Download both of them into your pc
2)extract both of them out.
3)Get the contents of both extracted folders and copy into the root of your sd card.
============================================================
The Actual Installation Process
1)Use either adb shell or Terminal Emulator(from the market) to install it
2)Enter the script below.
Code:
1.su
2.mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
3.cat /sdcard/flash_image > /system/bin/flash_image
4.chmod 755 /system/bin/flash_image
5.mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
6.flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
3)If you have error for step 5. stating /system/etc/install-recovery.sh : file not found, do not panic, just move on to the next step.
4)If you have error for flash_image : 1:")" unexpected, make sure flash_image is a file, not an folder.
============================================================
Testing it Out.
1)If you only had the error for step 5 from all of the above and nothing else. Pray hard and type in : reboot recovery into your adb shell or terminal emulator.
2)If you had errors from steps other from step 5, go look at it again and think. DO NOT TAKE THE RISK!
3)I'm still a newbie coder so this thread may not be good but I derived the files from here but I wanted to make it less confusing for you people so if there is anything missing/wrong/you don't know/you wanna ask, just post a reply!
=============================================================
Basic Key mappings for Custom Recovery:
menu > select
vol+ > up
vol- > down
back > back
Rest can be found here
FOR PEOPLE WHO THINKS THIS IS STOCK RECOVERY, IT IS NOT. IT ALLOWS FLASHING.
Nice Thread .....nut der r many threads same ...rite??? but i liked....i voted u !!1
Thaannkksss.....There are many threads, but most of which give confusing instructions that clearly do not work with idiots like me XP
amosng1 said:
Thaannkksss.....There are many threads, but most of which give confusing instructions that clearly do not work with idiots like me XP
Click to expand...
Click to collapse
rite.....depends upon person whos reading...
virusshah1997 said:
rite.....depends upon person whos reading...
Click to expand...
Click to collapse
True, thats preettty much why it has a unique title
Am running on stock 2.2.2 and rooted using GingerBreak. Whenever I try entering commands on Terminal Emulator it says Access Denied. Help!
bindaasathar said:
Am running on stock 2.2.2 and rooted using GingerBreak. Whenever I try entering commands on Terminal Emulator it says Access Denied. Help!
Click to expand...
Click to collapse
Hmm? Give more specific details. But try and see if you have root. If you have root but still says Access Denied, try typing su first?
amosng1 said:
Hmm? Give more specific details. But try and see if you have root. If you have root but still says Access Denied, try typing su first?
Click to expand...
Click to collapse
it says with I type in su the terminal emulator. My device is perfectly rooted since all other applications which require root access seem to work.
Thanks this is such a good info!
bindaasathar said:
it says with I type in su the terminal emulator. My device is perfectly rooted since all other applications which require root access seem to work.
Click to expand...
Click to collapse
No offense but what is "it says with i type...."
I kinda do not understand.
daniequy said:
Thanks this is such a good info!
Click to expand...
Click to collapse
Thank you.....maybe you could do me a favor and press that thank button
amosng1 said:
No offense but what is "it says with i type...."
I kinda do not understand.
Click to expand...
Click to collapse
If you had Superuser, did you allow terminal emulator to access root functions?
-a thought i have thought-
The sooner you reply, the faster i can get you a answer!
I got the following error in the last step 6:
Code:
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
I'm going to try to search for this issue but meanwhile if anyone knows what to do about this please let me know. I'll update a link here in case I find the solution.
Edit: This problem is fixed!!
If you get the out of memory error you need to type:
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
Reference: I got this from this link here in section 3.
amosng1, If you think other people might also experience the same issue then it would be great if you could precede Step 6 with the code above.
This worked perfectly fine for my LGP500 model! I booted into recovery.
ROM: Stock GB 2.3.3.
Kernel: Stock kernel (will update this detail on robooting my phone)
Rooted: Using SuperOneClick method with npeuter
Thanks a lot for your guide matey!
I, have already made a, thread for recovery with terminal emulater
http://forum.xda-developers.com/showthread.php?t=2003080
androidisfuture said:
I, have already made a, thread for recovery with terminal emulater
http://forum.xda-developers.com/showthread.php?t=2003080
Click to expand...
Click to collapse
Okay, I had used the adb shell actually. I've been more comfortable with this. Maybe I'll try out the terminal one sometime too.
Sent from my LG-P500 using xda app-developers app
Sorry, after each command what key i press to work? Or after step, how to work this command?
1.su
2.mount-o remount, rw-t YAFFS2 / dev/block/mtdblock1 / sistema
3.cat / sdcard / flash_image> / system / bin / flash_image
4.chmod 755 / system / bin / flash_image
5.mv / sistema / etc / install-recovery.sh / sistema / etc / install-recovery.sh.bak
6.flash_image recuperação / sdcard/recovery-RA-thunderg-2.2.1-GNM.img
One of the easiest how-to's I have come across
amosng1 said:
Okay, I seriously had enough of people saying is this AmonRa or whatsoever. I Derived both files from here and decided to make those instructions/script easier for you to understand. This recovery covers most basic needs (wipe,backup,restore,flash etc.) , so if you are going to keep complaining about my thread title/contents, I'll be glad to remove this thread and leave you people to figure out how to install custom recovery
WARNING : Only for P500....
Many people tried installing custom recovery, but ended up hard resetting your phone wondering WTF went wrong right? Like you people I ended up resetting 4 times =.=ll so..now I've succeeded, I'm just gonna share how its done!
==============================================================
Files Needed :
recovery-RA-thunderg-2.2.1-GNM.img.zip
flash_image.zip
(Both downloadable from below)
==============================================================
The files preparation process:
1)Download both of them into your pc
2)extract both of them out.
3)Get the contents of both extracted folders and copy into the root of your sd card.
============================================================
The Actual Installation Process
1)Use either adb shell or Terminal Emulator(from the market) to install it
2)Enter the script below.
Code:
1.su
2.mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
3.cat /sdcard/flash_image > /system/bin/flash_image
4.chmod 755 /system/bin/flash_image
5.mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
6.flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
3)If you have error for step 5. stating /system/etc/install-recovery.sh : file not found, do not panic, just move on to the next step.
4)If you have error for flash_image : 1:")" unexpected, make sure flash_image is a file, not an folder.
============================================================
Testing it Out.
1)If you only had the error for step 5 from all of the above and nothing else. Pray hard and type in : reboot recovery into your adb shell or terminal emulator.
2)If you had errors from steps other from step 5, go look at it again and think. DO NOT TAKE THE RISK!
3)I'm still a newbie coder so this thread may not be good but I derived the files from here but I wanted to make it less confusing for you people so if there is anything missing/wrong/you don't know/you wanna ask, just post a reply!
=============================================================
Basic Key mappings for Custom Recovery:
menu > select
vol+ > up
vol- > down
back > back
Rest can be found here
FOR PEOPLE WHO THINKS THIS IS STOCK RECOVERY, IT IS NOT. IT ALLOWS FLASHING.
Click to expand...
Click to collapse
Worked perfectly had only the step 5 error 'no such file or directory' everything else worked and I was able to boot into the custom recovery no problem. Thanks
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
ramongarza said:
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
Click to expand...
Click to collapse
could you list what rom you were on and what steps you took to flash cm7.1 please?
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
ramongarza said:
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
Click to expand...
Click to collapse
what recovery did you use to flash cm7?
Clockworkmod then later I tried rom manager. Does that answer your question?
Sent from my SCH-I500 using XDA App
follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1212239
i loaded the Rom thank you so much man!
Got CWM installed, and CM7 installed and running. superuser is there, but doesn't show any apps yet.
I installed titanium Backup and ran it, but get this error:
Sorry, I could not acquire root privileges. This application will *not* work! etc etc..
It mentioned verifying that busybox was installed, so I went to the market and downloaded the one by jrummy16, tried to run it, but it errors out - no root access.
Then I tried the one by stephen - same issue.
superuser v3.0.5 (39) is installed. It auto-updated to that immediately after the first full boot on CM7 with the market installed.
EDIT -
I uninstalled the superuser update, but still have the same issue. Downloaded rootchecker from the market, here is the output:
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
ls: /system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location:
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SCH-I500 device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae
Ok, so I followed the instructions here: (I can't post links ;( email me for the threads i went to)
and hereI can't post links ;( email me for the threads i went to)
and when trying to install su-2.3.6.1+busybox1.19zip, I get the following message - "E:Can't symlink /system/xbin/su
E:Failure at line 8:
symlink /system/bin/su SYTEM:xbin/su
Installation aborted."
What on earth did I do wrong???
No replies in 7 months? I too am struggling with this. Any help is appreciated.
That is because you can't flash that file via cwm. You need to push the files using adb. In addition I would suggest droidstyles guide because it spells out everything you need to do.
Sent from my SCH-I500 using Tapatalk 2
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
franky_402 said:
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
This procedure worked for my TF201 with partial root after updating to 4.1.1. The only issue was step 11, the forced update of Superuser's su binary. The message was “Making sure new su works..." but the result after several minutes was still "Waiting....". Should I rerun the forced su update? Despite this Vodoo OTA Rootkeeper did restore root without problem and Root Checker says thumbs up.
At this point, is there anything to do like switching to SuperSU that would make the root more future-proof?
Thank You! I have been trying to regain root after jellybean ota on my Motorola Atrix HD for the last week and a half. Finally success . I cant thank you enough!
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
You should be able to switch to a different root app. Never used this method but I have switched from superuser to supersu. Install superuser and run the binary update. Should tell you your binary is out of date with the name of the binary for the other root app. Update and reboot, then go back to superuser and check the binary update again. If it says it's up to date, uninstall the old root app and move superuser to /system/app. Reboot and you're good to go!
Sent from my Atrix HD MAXX
i think i tried that. istalling and uninstalling and subdstituting su and supersu. was not updating no matter what. also my adb push was not working so i copy pasted the su with my laptop while in adb shell. also updated su binary while in shell. it was already a system app from my previous attempts. anyway im good now
any one get it to work with no root/first time root? my prime wouldnt update via ota once on ics so i had to use the sd card update method to update. and from then on i never rooted again i then updated to jb and until 2 days ago i wanted to reroot but noticed there was no root method for jb yet. voodo root keeper just has super user app installed and ./system supports root protection both checked.
I'm in the same situation as fcortes626, I had to upgrade via sdcard method, and voodoo root keeper didn't maintain the root. I can't find any su backup in my filesystem.
I wonder if we can downgrade using the sd card update then root and go on from there........?
Sent from my SGH-T999 using xda app-developers app