NOTE 1: I have only tested this on 1.5.7 from AT&T.
NOTE 2: It could **** up your device, use at your own risk. Mixing a Telstra shared library (v2.2.2) in our ATT 2.2.1 system is an ugly hack
... but, it fixes Skype.
Requires: root. adb. smarts.
You can do the following steps, OR, apply libaudio-new-cwm.zip in CWM...
1. adb push libaudio.so /data/local/tmp
2. adb shell, su, "mount -o remount,rw /dev/null /system"
3. "cp /system/lib/libaudio.so /system/lib/libaudio.so.orig"
4. "cp /data/local/tmp/libaudio.so /system/lib/"
NOTE: Next steps cannot be skipped if you are using "Root Explorer" or some other method besides adb to copy over your old libaudio.so:
5. "chown 0 /system/lib/libaudio.so"
6. "chgrp 0 /system/lib/libaudio.so"
7. "chmod 0644 /system/lib/libaudio.so"
(sets mode to -rw-r--r--)
Enjoy your audio apps! Reboot doesn't seem to be necessary, the audio services crash and restart when the library is copied over. Hopefully we'll finally get a proper fix for this from the next OTA update.. you may want to return libaudio.so ("cp libaudio.so.orig libaudio.so") before you apply any OTA, so your system is virgin.
WARNING
This mod can cause a boot hang if you do it wrong. If you wanna be safe, please do the following (hopefully except step 3 ):
1. Have Tenfar's CWM installed first!!
http://forum.xda-developers.com/showthread.php?t=1019143
TO GO BACK TO OLD (BROKEN) 1.5.7: Copy libaudio-recover.zip to /sdcard
TO USE NEW WORKING (TELSTRA): Copy libaudio-new-cwm.zip to /sdcard
2. Use CWM to apply new libaudio (or return to stock with 'recover.zip')
IF something happens and you want to recover your original (see NOTE below for non-ATT 1.5.7 users):
3. Start CWM, navigate to "Install zip from SDCARD" and "choose zip from internal sdcard" and pick libaudio-recover.zip from within CWM (to start CWM: pull battery after hang and then plug Atrix to a wall charger, NOT a PC usb hub and re-insert battery) This will bring you back to the old, non-working 4.1.57 libaudio.so.
NOTE:
If you are not on AT&T and 1.5.7 then copy your original libaudio.so into the libaudio-recover.zip and recompress libaudio-recover.zip (using 'deflate' [usually the default] setting ONLY.) Then put it in /sdcard before you tinker...
Or better yet, use CWM to make a backup of your whole system which you can restore later... trust me, you won't regret it!
But so far, most have no problems with this mod... PM me if you do!
Confirmed working: Skype, Fring, Evernote, Nimbuzz, AudioTool, RTA Pro ...
Not yet working: SipDroid
Thanks.... Trying now.
Nice, hope this fixes my Audio Tools.
eval- said:
NOTE 1: I have only tested this on 1.5.7 from AT&T.
NOTE 2: It could **** up your device, use at your own risk. Mixing a Telstra shared library (v2.2.2) in our ATT 2.2.1 system is an ugly hack
... but, it fixes Skype.
Click to expand...
Click to collapse
Testing, will report in a bit
--
Works awesome... Thank you very much buddy. You made my day. Glad Påsk!!!
--
Checked Nimbuzz and Fring, they work too.
Fixed the issues with apps such as AudioTool and RTA Pro also.
Thanks again.
Awesome work! Trying this out now!
shouldn't it be "mount -o remount,rw...."?
eval- said:
Confirmed working: Skype, Fring, Evernote, Nimbuzz, AudioTool, RTA Pro ...
Click to expand...
Click to collapse
how about sip services?
like sipdroid..
Paschalis said:
how about sip services?
like sipdroid..
Click to expand...
Click to collapse
About to try... =)
EDIT: Nothing =( Either choppy or no audio at all on either end. =/ Anyone else with more luck?
Works great on Skype downloaded from market.
Any Skype with video and security patch available yet?
SUPER! it works perfectly now
Ouch, I replaced the file with root explorer, got a backup of the old libaudio.so in the same folder, and after reboot phone gets stuck at Motorola Dual Core with red led flashing.
Is there a way to recover it (e.g. a way to restore the old file which I have as libaudio.so.org in the same folde) without flashing back to the stock rom or with a hard reset? (I am lazy to reconfigure everything).
fincan said:
Ouch, I replaced the file with root explorer, got a backup of the old libaudio.so in the same folder, and after reboot phone gets stuck at Motorola Dual Core with red led flashing.
Is there a way to recover it (e.g. a way to restore the old file which I have as libaudio.so.org in the same folde) without flashing back to the stock rom or with a hard reset? (I am lazy to reconfigure everything).
Click to expand...
Click to collapse
had the same issue, when i was messing with framework-res.apk ..
i did restore, via Tenfars recovery..
if you made a working backup before, you can advaced restore, and restore only your system..
i dont know if there is a better method.
eg to restore your backup of libaudio.so via adb.. i would be great
fincan said:
Ouch, I replaced the file with root explorer, got a backup of the old libaudio.so in the same folder, and after reboot phone gets stuck at Motorola Dual Core with red led flashing.
Is there a way to recover it (e.g. a way to restore the old file which I have as libaudio.so.org in the same folde) without flashing back to the stock rom or with a hard reset? (I am lazy to reconfigure everything).
Click to expand...
Click to collapse
Hum? You just did the same exact steps via root explorer instead of adb and the result is a hang on boot? Were you on 1.5.7? If you have clockworkmod I can whip up something quick to try and help you, but you need to have a micro sd card. This is assuming that libaudio.so is why you cannot boot, but I didn't realize it was loaded quite so early, I've done very early mods and my hangs come during the "rethinking possible" and I have no LED activity. PM me if you have CWM.
Paschalis said:
had the same issue, when i was messing with framework-res.apk ..
Click to expand...
Click to collapse
So you think another mod made you hang, not this libaudio, right?
Paschalis said:
i dont know if there is a better method.
eg to restore your backup of libaudio.so via adb.. i would be great
Click to expand...
Click to collapse
I don't think there is a better method but I could make a restore-audio.zip for you to run from Tenfar's CWM. (Perhaps I should've done this before posting!)
I don't have CWM on the phone. Guess I am hosed haha. Oh well.
Can I apply this to Bell Atrix?
ytwytw said:
Can I apply this to Bell Atrix?
Click to expand...
Click to collapse
Is Bell Atrix unable to use skype? You can try but why don't you first install Tenfar's CWM and PM me if you have any issues... are you rooted? CWM is very useful to have. I can build a recovery zip for you in case it fails and you can put it on /sdcard before you try the libaudio hack.
Can I load CWM via NVflash as explained in this link:
http://forum.xda-developers.com/showthread.php?t=1047792
And recover with a script? Or do I need a fully booting phone to install CWM via NVflash?
Related
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
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 put together some steps to take your fresh KA6 2.2 Official update and add Root and ClockworkMod Recovery. It may look hard, but should only take a couple minutes.
This is without ODIN or ROMS.
Steps:
0. Have yourself a T-Mobile Vibrant and PC Running Windows.
1. Use SuperOneClick (latest) to root phone. When you run the application, click the first button on the left and wait for the process to complete. Details will be scrolling in the middle window.(http://forum.xda-developers.com/showthread.php?t=803682)
2. Use a file manager (ROOT EXPLORER) or adb with root access to mount /system/ and remove bloatware (SLACKERRADIO and AMAZONMP3 and such) from /system/app/
2a. TOTAL NOOBS: Get SUPER MANAGER from the market (FREE). Then grant it root by going into SUPER MANAGER and selecting File Manager > [Menu BUTTON] > Setup > Enable ROOT function. Then go up levels, the top button on the file manager which will take you up a directory, until you get to / and scroll to the bottom and select [system]. Then select [app]. Then click [Menu BUTTON] > Switch System to R/W and press R/W. Scroll down and long press the slackerradio.apk to delete. You can do this too amazon market to delete and other useless apps.
3. YOU NEED STEP 2 TO DO THIS STEP! Install Busybox from Market and run Busybox Installer to ensure its properly working and the latest is installed.
4. Run SuperOneClick again to place phone into shell root ADB (Second button from the left). Allow the process to run and then a pop up will say something about rebooting the phone. DO NOT DO THIS, continue on to the next step.
5. While in shell root from the previous step, run (3e) to (2e) modified recovery script. The instructions are simple. Download, unzip, and run the batch file found inside. This is ran from the COMPUTER NOT YOUR PHONE. Use the menu system to complete and then reboot as recommended. (http://forum.xda-developers.com/showthread.php?t=833423).
5a. NOT NOOBS: you can copy over the recovery yourself to /system/bin as mentioned by some commenters. If you do not know what this is, then ignore it.
6. Remove any update.zip files from /sdcard/ and also remove any ClockworkMod directories using your favorite file manager or by mounting to a computer with a wire and activating the drive for My Computer. This is the internal one, not external.
7. Use ROM MANAGER from market to install ClockworkMod Recovery and reboot. This is free to download. When you launch, select the top item to install the recovery and then a menu will pop up to choose the phone you have. Happily select Vibrant. Once that's done, select reboot into recover right below that.
8. Re-install packages and it should reboot. You can navigate the menu using VOL UP AND DOWN and power to select.
9. Re-install packages again and it should boot into Clockwork Recovery. It should change form BLUE TO GREEN
ALL DONE.
That should do it for ya! Let me know if it worked out. Please follow all steps and don't cut corners.
Should you need to get back to ClockworkMod Recovery, you can use "adb reboot recovery" and re-install packages, or reboot into recovery with ROM MANAGER.
Edit Rev.a: added a step (6) Made the instructions more precise and added additional steps to clear up some confusion.(1-22-11)
Edit Rev.b: Added step 2a from request. root explorer is not free so use super, that works too. (1-24-11)
Edit Rev.c: Added more detail to the steps and added supplemental info for replacing the recovery with the modified one. (1-27-11)
Edit Rev.d: Super1Click has updated, so latest? works.
Side note: I do step 4 because from my experience, I had trouble getting the modified 3e script to get root. Figured might as well just give it root to begin with.
Side note: Yes I am aware that there are other methods and different ways. This was the noob way for me to convey it to the masses. I still do appreciate all feedback regardless of what it is. Thanks!
jmcghee1973:
***For kicks you can do your 2.2 KA6 update the download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
***For kicks you can do your 2.2 KA6 update then download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
Not to hijack your thread...
Yea I know, but I wanted to find a way without ODIN.
added ur blurp
Reinstalling packages does not seem to work for me. Every time I click it and it reboots it keeps going into the samsung recovery menu... Help?
Does it give an error for signing or just looks like its working then reboots?
Looks like it works and then reboots
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card changed directories with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Nothingness00 said:
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card stopped working with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Click to expand...
Click to collapse
Tried that, still can't get into clockwork recovery...
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/
I would highly suggest doing that step. The system is full to begin with. Use Root Explorer and grant access, then mount system into r/w and remove the stupid stuff. You should do this to get Busybox on (AS IN BEFORE YOU INSTALL BUSYBOX)
What does busybox do?
jmoreau10 said:
What does busybox do?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/BusyBox
ITS ESSENTIAL
Got it working man, thanks.
Awesome! Good to hear. This is my first tutorial and I'm stoked that its working well for others.
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
dsilver981 said:
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
Click to expand...
Click to collapse
4. Run SuperOneClick again to place phone into root shell ADB
For this step, run SuperOneClick from before, the same you used to root. The second button says "Shell Root". Click that Wait for it to say you have shell root until you reset.
5. Run (3e) to (2e) modified recovery script (http://forum.xda-developers.com/showthread.php?t=833423)
Just download the attachment in the first post and follow instructions. Its fairly simple process. Keep in mind, this may not work unless your phone is shell root from step 4
Thank you Nothingness. Cleared it right up. Worked perfectly.
dsilver981 said:
Thank you Nothingness. Cleared it right up. Worked perfectly.
Click to expand...
Click to collapse
Awesome! Great to hear it! Love them thanks
im a total noob, but im about to try this, wish me luck haha
thoetherguy said:
im a total noob, but im about to try this, wish me luck haha
Click to expand...
Click to collapse
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Nothingness00 said:
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Click to expand...
Click to collapse
haha, yeah it was easy , thanks...
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
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