Related
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.
i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.
Click to expand...
Click to collapse
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero
Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.
il Duce said:
Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.
Click to expand...
Click to collapse
i installed the rom manager from apk. the market wouldn't download it for some reason. but it wont let me install the recovery, it says i dont have a reliable signal, which i do.
laie1472 said:
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero
Click to expand...
Click to collapse
check, check and check.
i have two on the root of my sdcard named, recovery.img and the other one is recovery-RA-heroc-v1.5.2.img they are both the same file, i just used recovery.img as instructed in the old how to root by regaw, back when i knew what i was doing, ahaha.
Sent you a pm
Sent from my HTC Hero CDMA using XDA App
just a wild guess, but how about
flash_image recovery /mnt/sdcard/recovery-RA-heroc-v1.5.2.img
?
UPDATE(Feb 07, 2012): Updating this with most recent info and installation instructions:
ROW 16GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=381ventana_recovery_row_16.img
ROW 32GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=165ventana_recovery_row_32.img
ROW 64GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=656ventana_recovery_row_64.img
Again, use at your own risk. 32GB and 64GB versions have not been tested.
NOTE: Backup has been tested, but recovery hasn't, though I'd be surprised if it didn't. This is a USE AT YOUR OWN RISK image. Also, I noticed my tablet rebooted once or twice while attempting to backup. This was likely due to the 9% battery indicator, but I figure I'd warn you just in case. If you leave your tablet to backup and you get back to it and you see your launcher unlock screen, it rebooted and likely didn't finish so you'll have to try again(again, I'm pretty sure this was just due to me having run down my battery).
WARNING: The following assumes you haven't installed any CWR image yet. If you've already installed CWR successfully, follow the 'Update Steps'.
Installation Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
Uninstallation Steps:
Code:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Update Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/dev/block/mmcblk0p1 of=/data/local/recovery_backup_image.img
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
If CWR randomly reboots on you when you either try to do a backup or simply stay on the menu too long, try the following(thanks stewarta):
Boot into CWR. Then select to reboot the device(not "Reboot recovery", just the normal reboot).
Allow it to boot into full Android.
Reboot the device again and re-enter CWR. It should no longer be rebooting.
I don't know why the above happens or fixes it. If it doesn't work for you, please do the following:
Boot into CWR. Either wait at the menu screen or attempt a backup(we want to provoke a reboot)
On reboot, hit Vol+ to enter CWR again.
Select 'Advanced'.
Select 'report recovery'. It will tell you at the bottom where the log is stored. Make a note of it.
Boot into full Android and use your favourite file manager to get the log. Paste its contents in this thread.
And once again thanks to Koshu, logxen and jcase and everyone else involved. They did most of the work. I mostly just hit "make".
____________________________________
So with that out of the way:
The kernel is the only change between jcase's port and the ROW version. The BuildConfig and such are untouched.
So why does it work? I would imagine a recovery image would be beyond caring about region of even the kernel version of the main OS. I can't imagine they'd have altered the hardware between builds, especially as ROW merits as much attention as bundling Canada and Berlin...
So, any ideas as to what could cause the difference? Could it be the nvflash signing keys? Could there be a driver inconsistency? Anyone have any ideas on how to troubleshoot at that level seeing as it doesn't look like Android even logs anything that early in the boot process.
Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.
fhing said:
Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.
Click to expand...
Click to collapse
I didn't do anything but make using the ROW kernel extracted from my tablet. Koshu and jcase deserve those thanks more than I.
As far as a US image, go to the following post. Koshu has US CWR images for all models.
http://forum.xda-developers.com/showpost.php?p=21992089&postcount=106
Once again thank you realyst2k for compiling CWR for ROW.
I have TPT ROW 16GB. I backuped with no problem. Only one question, when backuping /data folder it skips /data/media folder which is internal memory same as /mnt/sdcard. From one side it's OK because it can contain up to 10G data and it would be hard to backup it, but from other side resetting to factory defaults also deletes /mnt/sdcard and so you need backup it also. I am little confused?!?!?! What is the situation in other tablets with internal storage?
It skips that mountpoint on purpose. I believe this is how the Transformer does it too. The reasoning aside from potentially gigantic backups and recoveries, is that it can also prevent a proper backup since it could easily overpower the filesystem on some SD cards(especially if you consider the 32GB model).
It's not needed in any case. CWR is made to do a NAND backup, which are your OS files and such. You can use Titanium Backup if you need to backup your media.
@realyst2k:
(SOLVED)
stewarta said:
@realyst2k:
I couldn't get this to work:
I followed the UPDATE steps but even though the file permissions are okay (rw-rw-rw) it could not read the file at the last step. Probably something simply ....
Click to expand...
Click to collapse
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
Thanks for the speedy reply. That was the first thing I checked .... the second was that I can still do Nand backups ... and I can. I'll copy it into the directory and try that command line again.
---------- Post added at 03:31 AM ---------- Previous post was at 02:54 AM ----------
realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
@realyst2k: Guess what it was .... the download file name is ventana_recovery_row_32.img. Compare that with the command line below ...
dd if=/data/local/recovery_ventana_row_32.img of=/dev/block/mmcblk0p1
So that was never going to work until I renamed the file. Duh! Boots into CWR, so I did my usual trick of booting into CWR, doing nothing and booting back into Android OS. Now back in CWR and doing a Nandroid backup without any issues at all. So thank you once again.
Might uninstall CWR over Easter and get OTA2. Perhaps not ... might just wait for ICS in May/June.
OTA 2 and Root with CWR
@realyst2k Being impatient, I decided to rename the install-recovery.sh and the install-recovery.sh.forrecovery and install the OTA and see what was what.
It installed fine. I've lost root, so I will have a go at using the original method of rooting the TPT. Oddly, Root Explorer works, but SuperUser (chainsdd) is not logging this fact. NSTools seems to work as well (reports the scheduler is Noop).
Anyway, long story short, I will report more tomorrow. When I have more time.
Happy Easter.
OTA2 = No Root
(SOLVED)
OTA 2.5 + Root + CWR
Yay! I am back in business with root after installing OTA 2.5. For the low down, use this new exploit. But make sure you have the right drivers and lines in the android_winusb.inf file (Do a check using adb devices in a command window while the TPT is connected and in recovery mode. If no device is reported go into Win Device Manager and check out if you have Android phone showing or Portable device with a MTP driver--the latter is WRONG and you need to get the correct driver loaded otherwise you get the errors being reported by many others):
Code:
[Google.NTamd64]
;
;NVIDIATegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra %SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741C
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;
;Lenovo Think Tablet
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741B&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741D&MI_02
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741E&MI_02
His script does work. Even without a factory reset. So now I have 0089_ROW with root. And yes, I am now using 'Root Keeper' from Play Store.
And before you ask, realyst2k's method of gaining CWR works. Just make sure your first boot in CWR is only to reboot back into the OS. Then on your next boot into CWR, you can do a Nandroid backup without any unintended boots and the like. This means boot into CWR from shutdown using Vol+ and Pwr, then Vol+ after the vibration (do not use such as Rom Manager). Enjoy!
Doesn't work for my TPT 64GB.
I'm ready to trace/play/debug/... to get it work
I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.
josh451 said:
I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.
Click to expand...
Click to collapse
Yes, I think that as long as the Android phone driver from Lenovo is there it will work. But if it is Portable Devices > MTP USB Device on its own, it will not. Well done!
I'm an idiot !
Links are not dead, for those looking for files you need to wait for a reservation ticket. Too impatient
Great work, thx!
As a TPT 32Gb user, had to rename files on cmdline then all went well.
Just one question: any way to activate emmc instead of using external SD to work with recovery?
I do know it is achieving by patching recovery.fstab, but don't know what exactly should be added..
As for differencies:
My try was to install WE system image on ROW, I succeed. After trying to install also boot image it loops at first lenovo logo.. and as kernel source is common the remainig thing is ramdisk oO
i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.
the problem was resolved. need to recover after the stock bootloader
adb shell
$ su
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
TWICE TPT reboot, reboot, and the second is already possible to enter the recovery boot (Vol+)
---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------
new problem: how to install the CWM on 0121_ROW firmware. instruction from the first post does not fit.
CWM Recovery and ICS 4.0.3
Anyone got a CWM Recovery for ICS 4.0.3. ICS sure brings the TPT alive ... but I'd like to be able to do a Nandroid backup so I can stay that way. OTARootkeeper ensured I have root access, so that is a big help.
---------- Post added at 08:16 AM ---------- Previous post was at 08:03 AM ----------
Driver'z said:
i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.
Click to expand...
Click to collapse
Slip across here as there may be quite a few reasons for this.
I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.
Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.
Checked...thanks. =) Added the links.
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.
I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2
Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)
0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?
I have my wife's LG Revolution running Broken Out rom. I am getting to read to send int to big read for a replacement. They made me state that I had made not hardware or software modifications. So I need to return this to stock. I have successively used LGNPST in the past. But now the USB port does not work in data mode. A computer will charge the phone, but the phone does not prompt for USB Mode when plugin to a computer. I have tried 2 computers and 2 different cables. All of which work for my LG revolution with out a problem.
Is there any way to remove Clock Work mode and switch it to the factory recovery, and return the rom to Stock without a working USB port?
I have a way of copying files to the SD card if needed.
Thanks.
I like this this guys thoroughness, though, not totally relevant for you. The following steps would pertain best in your situation.
1) wipe data, cache, davlik cache from CWM
2) When the phone initial setup begins, bypass it with this method. Touch top left, top right, bottom right, then lastly bottom left.
3) OPTIONAL - Erase external SD card from settings menu (if you thnk it's necessary... you may not be sending that back in)
4) format internal memory from settings menu
5) LGNPST flash stock V9. Get the V9 TOT here and unzip it first.
Flashing the TOT just took me 20 minutes.
Really, though, just flashing the TOT will suffice.
That's very neet, thank you. But can I use LGNPST without a usb cable? My usb port will only charge, no data.
Sent using Tapatalk 2
Whoops. Missed that part. I was on a roll doing a TOT via USB myself. Maybe, if someone could wrangle you up a stock boot.img to flash in CWM after you unroot?
Sent from my VS910 4G using Tapatalk 2
If someone who is running a stock rooted rom, v9 or later, wants to put up a backup I can rip the rom out of it and make a flashable zip. Just when making the backup, go into the backup settings of cwm and change it to tar.gz. Not the blob crap.
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
thesavo said:
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
That would be awesome! To have at least the android part of the new update is better than nothing.
He still needs to find a way to remove cwm with out a pc?
I don't have clockwork on my stock + rooted Revolution. Can I use any rooted backup tool from the market/play store?
IF i have to use Clockwork mod recovery, can I just do a nandroid backup from the good phone the other phone? I have to take in to big red tomorrow.
Does anything need to be stripped out of the nandroid back?
I was just trying to think of another way to get you going. ADB Wireless sounded good up until the point that the SU part has to be removed. Then ADB Wireless would fail I'm sure.
My best guess for you is to use the Easy V8 - V9 All in One by Mark Once Again as a basis for commands to execute from terminal. I'm not sure if losing root during terminal will affect the operation however. Looking at the batch file adb shell commands, it looks fairly straightforward to manually do. I am just not 100% sure it will work. Someone else with more experience could chime in about that.
Below is what I copied out of the batch file, the UNROOTSTOCK portion.
The ALL CAPS portions are comments I have added in. The usual warnings apply. Use at your own risk.
Code:
rm /data/bootlogo/bootlogopid
ln -s /data /data/bootlogo/bootlogopid
REBOOT
echo 'ro.kernel.qemu=1' > /data/local.prop
REBOOT
UNROOTING TIME
rm /system/bin/su
rm /system/xbin/su
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/bin/busybox
rm /data/local/tmp/* 2>/dev/null
USE A ROOT FILE EXPLORER APP TO COPY THIS Files\stockrecovery.img FROM THE EASY V8 - V9 ZIP. . .
TO HERE ON YOUR PHONE /data/local/tmp/stockrecovery.img
TIME TO PUSH THE STOCK RECOVERY
dd if=/data/local/tmp/stockrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
CLEAN-UP TIME
rm /data/bootlogo/bootlogopid
rm /data/local.prop
REBOOT AND YOU'RE DONE!
Hope that helps, or that it spurs the help you need.
EDIT: To make it stock, all the superuser and busybox files need to be removed, and the stock boot image needs to replace the one that has CWM. Otherwise, CWM is still there. So, no. A nandroid from the other phone wouldn't help you.
But would a restored nandroird backup (from my phone) work enough to get me 1/2 way there? Would the nandroid restore leave me with
Rooted Verizon rom
Clockwork mod recovery.
If so. I could DD the stock recovery over clockwork mod recovery.
Then unroot it with a terminal app.
By the looks of your pseudo-code script, It does do all of that, in a different order.
It's possible to capture a stock, unmolested nandroid, but that would be from a bone stock phone with CWM I think. A dev did that for us on the Nabi 2, making a stock image before the rooting business. Then it's just getting the stock boot image back, if you catch my drift.
I could have done it a couple days ago having just reTOT'ed...
Edit: The Nabi is a tablet and I think some have shared their images, but I don't know if there are any implications sharing a phone nandroid.
Sent from my VS910 4G using Tapatalk 2
I have two of these VS910s. I just cleared out my internal SDCard on my VS910. It's rooted running the newest verizon rom. It doesn't have CWM right now, but is that required for nandroid backup? To restore to my wife's with the busted USB port? I'll run the backup to my sdcard then place it in her phone to run the restore.
Needing CWM. . . no. I was going to say yes, but there is a way to make a nandroid with your phone on. Using Online Nandroid, or an app developed based on it, Orange Backup, you can make an image with your phone on, no need for CWM. It will need a patch file installed, but I already got that going with the dev. It looks like it will work for the Revolution. One caveat. While I tested that it successfully backed up my phone, I didn't actually restore the nandroid created.
Looking into the Nabi's stock backup during rooting and recovery, the dev used TWRP instead of CWM. TWRP supports Open Recovery Scripts which he used to do a stock backup. No go for us with CWM, at least not how he did it. No matter because your phone is rooted.
OK, so I installed CWM recovery on my working phone. No big deal. I took two backups for good measure on the bad phone. I also restored one of the backups, it seamed to work.
I am taking a backup of my rooted stock phone. I will then attempt to restore it to the bad phone. Any thoughts to using DD in a terminal app on the phone? I should then dd the recovery.img file over CWM,
To unroot, i think i shuld be able to do as you suggested to delete SU.apk and busybox.
Good luck. Dinner is served now so I'll be missing for a while.
Bait-Fish said:
Good luck. Dinner is served now so I'll be missing for a while.
Click to expand...
Click to collapse
We have stupid verizon 4G LTE boot video on the bad phone. That's a good sign.
Edit: Its running a VZW rom now!
home stretch
Ok, so after restoring a Nandroid backup of verizon's VZB to the bad phone. Now I need to un-root it. and I should be good. Also, Settings -> about says its version VZ9 not VZB. Odd.
Plan.
Add my google account to get to play store.
Add a terminal app.
Use terminal to delete any nandroid backups.
Run DD from terminal to overwrite CWM with recovery,img
delete rooted files.
Run factory wipe. from settings menu or PWR + Vol Down.
Then I should be done
Any thoughts.?
Seems about right. The version won't tick up from VZ9 unless you do the actual OTA I understand. Something about the baseband.
Sent from my VS910 4G using Tapatalk 2