Related
I have downgraded from JPK to JM8. When recovery runs I get an errormessage about "can not access /system/csc", not exact words but I think I've understood it right. I have checked it with ADB and I have permissions set to "drwxr-xr-x root root csc" and in /system/csc I have "-rw-r--r-- root root" on all files. It seems a little strange that my permissions are set to that in the folder. Are those permissions correct?
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Ok. Will do that. I'm looking for a reason to why I can't flash docs rommod onto my phone. I can't get any further than to the S on black background hearing bootsound but the phone doesn't boot up to a ui. Thought the message could be a clue to that problem
did you do a factory reset in recovery?
When do I have to do that factory reset? I have tried to do it after the slimmod flash. Should I do it before flashing the mod? Now I have oclf installed. Do I have to remove it before trying again?
I have done a clean install of JM8. Installed OCLF, rooted, installed RomManager and clockworkmod recovery. Pushed extreme superslim to internal sdcard. Rebooted into recovery. Did a factory reset and wipe of cache. Installed zip from sdcard. ONLY DIFFERENCE IS THAT MY CLOCK SHOWES TWO HOURS TO EARLY. What am I doing wrong?
Install fresh jm8 push docs update.zip to sdcard and apply it. Then install those rest...
Sent from my GT-I9000 using XDA App
At last! After to more resets and flashes I have Extreme Slim on my device and I really likes it. Big applause to doc. Happy HTC:ing.
mickeko said:
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Click to expand...
Click to collapse
I noticed with this you had to change the permissions for these foders using a program such as root explorer. Tick all boxes. Well, that's the only way I got rid of the error.
Also case sensative..
/system is usually mounted a read-only, you have to remount it like this from terminal emulator (rooted of course)
$ su
$ mount -o remount,rw /system
then run
$ mount
you should see /system mounted as 'rw'
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...
Greetings everyone,
im new to this and im very very confused, i bought a galaxy note and i was able to flash the latest firmware ICS 4.0.3 (Open German), but what i cant do is rooting the phone, and what is the exact point im failing at is creating an SDcard folder on the internal memory, i dont have an external SDcard, and as i have read on other threads :
Step 1: Download the following files from the official thread [XDA-Developers]:
CWM.zip
SU-Busybox-Installer.zip
Place all these files directly under /sdcard on your device’s internal memory.
Step 2: Shutdown your device. Once it is completely shut down, press and hold Volume Down + Power + Home buttons until you see a screen asking you to press to press Volume Up. Press said button to complete booting into Recovery Mode.
Step 3: Select apply update from external storage and then navigate to where you placed CWM.zip. Select it.
Step 4: Your device should now boot into ClockworkMod (CWM) Recovery.
Step 5: From CWM, choose install zip from sdcard > choose zip from sdcard > SU-Busybox-Installer.zip
Step 6: From main menu of CWM, choose reboot system now.
If you followed the steps correctly, your Samsung Galaxy Note International GT-N7000 will now be rooted on Android 4.0.3 ICS.
all the steps seems to be easy, and i failed on creating sdcard folder on internal memory, i would appreciate your help.
thanks alot
hussam saidan
Just place the file of busybox etc in ur phones default 16gb memory... that is the internal sd card...
No need of creating anything...
still does not work...
sbnaul said:
Just place the file of busybox etc in ur phones default 16gb memory... that is the internal sd card...
No need of creating anything...
Click to expand...
Click to collapse
i did that, and when i tried to install, still tells me E:failed to load directories or file sdcard..
it's not working, and the guy says i should create a file in the internal memory which i dont think i can access, still need help, please someone help me out
hussamutza said:
i did that, and when i tried to install, still tells me E:failed to load directories or file sdcard..
it's not working, and the guy says i should create a file in the internal memory which i dont think i can access, still need help, please someone help me out
Click to expand...
Click to collapse
You need to put the zip file in the root directory of the internal memory (internal SD card). Then in CWM you need to choose install zip from internal SD card not from SD card.
finding difficulties doing that
tknguyencsu said:
You need to put the zip file in the root directory of the internal memory (internal SD card). Then in CWM you need to choose install zip from internal SD card not from SD card.
Click to expand...
Click to collapse
sorry for asking alot, but actually i dont know that much about androids, what i did step by step is,
1- downloading the files
2- open phone storage via my computer
3- pasted the files once the screen opened and created a file named sdcard and pasted the files there too just in case.
4- turned off the phone, pressed vol up+homescreen+power
5- apply updates from sdcard
and after that i wait a couple of seconds and a message pops in red says
E:/failed to mount /sdcard(no such file or directory)
i was never able to reach CWM.
if you could patiently and gladly post me a step by step what should i do, i will be very appreciated and thanks in advance.
thanks for helping
hussam saidan
bump bump
i would love to have an expert to guide me thru or give me step by step guide...
still needs help !!
I guess you are choosing the wrong option from the CWM
On the first screen of CWM recovery
1. choose "install zip from sd card"
2. On the next screen click "install zip from internal sdcard"
3. then goto the folder you created and then choose the SU zip file
Hope it helps...
need help
akhugsal said:
I guess you are choosing the wrong option from the CWM
On the first screen of CWM recovery
1. choose "install zip from sd card"
2. On the next screen click "install zip from internal sdcard"
3. then goto the folder you created and then choose the SU zip file
Hope it helps...
Click to expand...
Click to collapse
my friend, im not even able to reach CWM, my phone is not rooted, im trying to root my phone, i cant reach CWM. i just need a way to Root my galaxy note ice 4.0.3
Ok try this turn phone off, turn on and quickly
press volume up, home and power at same time untill phone boots again, this is tricky may need couple tries. This will launch recovery. From there choose install update from... By navigating with volume buttons you can choose install from. This opens the sd card, choose the folder where you downloaded cwm.zip to, navigate with volume button to it. Click power button to select., navigate to yes and watch it install, after install you can use touch screen to options described in your first post. This will install superuser. After that is done reboot. In applications there is superuser. You are rooted now.
Sent from my GT-N7000 using Tapatalk 2
I did everything you said exactly but I got only super now but no CWM! And when I access root by some application it says you need root.
Here is what I did
1. Boot into recovery
2. Select install from sd
3. Selected external sd
4. Choose CWM.zip
5. Confirm install
6. Now recovery booted onto CWM
7. Select sd card (internal)
8. Choose su busy box from root folder
9. Confirm installation
10. Reboot device.
Now I can only see busybox not CWM!!!!!
Sent from my GT-N7000 using xda premium
Ok progress, but not full root. Download speedmod kernel on your phone, the cwm flashable zip from developer thread k3.
Speedmod is prerooted, and should together with already installed superuser provide full root. ICS one is k3 thread. The k3-3 one is stable and relatively safe. Best batterylife too.
Now restart procedure with cwm.zip instal. In cwm install the speedmod kernel zip and reboot. Now you should have full root. Test it by rebooting, opening superuser and in preferences select update binaries. Allow superuser acces for superuser. Select update. It should pass everything.
Cwm recovery is now also installed, but not as a link within applications. You can access it by rebooting and volume up, homekey and power combo. Speedmod has the wipe functionality that can break your phone disabled, same goes for factory reset. If you want that in future install throught pc odin, see stickies development thread drKetans thread, and do it safely from gb, and not ICS.
Sent from my GT-N7000 using Tapatalk 2
You can download speedmod from the download lin in first post of this thread. Not the sourcecode, but from the download link.
http://forum.xda-developers.com/showthread.php?t=1673072
Sent from my GT-N7000 using Tapatalk 2
In subsequent posts it said there is bug for hard brick!!! Should I use only odin method?? If I do so will it increase binary counter?
Sent from my GT-N7000 using xda premium
priyanv said:
In subsequent posts it said there is bug for hard brick!!! Should I use only odin method?? If I do so will it increase binary counter?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
No, do the cwm.zip install, easiest. Odin is safest always, but because of triangle and binary counter I recommend cwm.
Just dont do factory reset/wipe from cwm. Thats what triggers the hardbrick in 99% of cases. Only small number of cases by installing through cwm.
Sent from my GT-N7000 using Tapatalk 2
I know rooting is completely upon owners risk... And m gonna take that now...
Sent from my GT-N7000 using xda premium
OK now I got CWM and superSU and speedmod kernel. But still I don't have root access. M trying to remove Google ads thru lucky patcher but it gives error that I don't have root access .. Is there separate version for ICS? I got moved all the alps from gb thru TB.
Sent from my GT-N7000 using xda premium
Did you test by updating binaries throught superuser preferences?
Actually, if you followed procedure you should have superuser and not supersu .
Get it here http://forum.xda-developers.com/showthread.php?t=1647148
Best to reinstall throught cwm the superuser zip. And test root again
Edit, unstall supersu first. Then after zip install test update binaries
Sent from my GT-N7000 using Tapatalk 2
Wow everything solved and I managed to remove ads.. Thanks for your patient help..
Sent from my GT-N7000 using xda premium
Your welcome
Sent from my GT-N7000 using Tapatalk 2
Should you want to revert to stock, follow guide from genius dr Ketan in sticky thread of development. Best to do that before sending to service centre because they dont like or akways accept rooted devices for warranty
Sent from my GT-N7000 using Tapatalk 2
**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!