Database Develop

Newb Questions

Hey folks,
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Any help is much appreciated

thatenglishguy said:
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
Click to expand...
Click to collapse
Yeah, that's what I do.
thatenglishguy said:
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
Click to expand...
Click to collapse
There are 2 parts to what you are doing. You are gaining root access, and then you are using that access the write a new recovery image to your phone. You may keep the standard ROM.
thatenglishguy said:
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Click to expand...
Click to collapse
You install new ROMs using the recovery image you installed while rooting your phone. Copy the .zip file(s) for the ROM you want to flash to the root directory of your sdcard. Boot to recovery by holding the HOME key while you press the power button. In recovery, you have the option to backup your existing ROM and to install a new one.

Thanks
Awesome, thank you v much indeed.

I have rooted my phone with Regaw's instructions, and it was very straight-forward.
1.) When you root your phone, you have a special recovery image that you can boot the phone into, and basically back up/restore your phone in case you decide to flash different roms and didn't like it, or you screwed up somewhere along the way. You can toggle the usb function, meaning you can use a terminal emulator (command prompt for windows) and move files between your pc and the phone while in recovery. You can theme your phone, can remove unwanted apps, use apps from the market that require you to have root access.
The simplest reason; to have full control of your phone.
2.) When you aquire root on your phone and able to boot into recovery and such, you can take the zip file that the rom was created in, and transfer it to the root of your sd card. Then you can either A) Open the command prompt, type in adb shell then type in reboot recovery while the phone is plugged in with the pc. The phone will reboot into recovery. B) Just power off the phone completely, then press and hold the home key and turn the phone on until you get to the recovery screen. From there you will need to backup your phone if you haven't already. Select backup/restore, then select nand backup. It will take a few minutes for this process to complete. When finished, you can go back to the main screen, and select wipe. Then select wipe data/factory reset. Press the home key to confirm. Go back and select wipe Dalvik-cache.
When done, go back to the main screen and select flash zip from sdcard. Scroll to the rom that you put in and select it. It should take a couple minutes to flash the new rom on your phone. When it's finished, you need to reboot your phone. The reboot process will take about 5-10 minutes depending on the type of rom that you flashed.
A few tips:
*Once you root, you have voided your warranty for the phone. But have no fear! Make sure you save your sdcard to your PC and run the RUU before bringing the phone for service if you need to. When service is done, you may transfer your sdcard contents from the pc back to your phone, do a quick root, and you are good to go.
*When wiping, your phone will be factory reset, meaning you have to sign into google again, redownload all your apps from the market if you have any.
*If you do like the rom of your choice, try to tweak it out the best you can, then do a nandroid (backup your phone) just in case you flash another rom. If you flash a second or third rom or whatever and didnt like it, you may do a restore on your phone, and all your info will be saved from the last nandroid you made. Be careful on how many nandroid you do. It takes up space on your sdcard. You may rename your nandroids, and remove the ones you don't want.
*The battery may get hot when flashing roms. This is normal, just try not to over do it.
*This Hero CDMA forum is now your best friend. Read and search, read and search before posting a question. Not that we don't mind answering questions, but if it has been asked 50 times, some people will give you snarky comments.
Good luck!

thanks , one more thing
Very helpful and I have successfully rooted my Hero !
Now regarding the new ROM I have downloaded the Zip file do I just copy the whole thing onto my phones sd card? If so where into the Nandroid folder?
Or do I run it using CMD from my laptop and if so know of any guides on how?
Thanks again, muchly appreciated
MB

Easiest way is you mount your phone to pc via usb, and just drop the zip file onto the root of your sdcard. Do not place the zip file anywhere else, or in any folder, just in the sdcard itself. Remount the phone, reboot into recovery, and select flash zip. Your rom should be in there to flash.

A wise man once said, "You've taken your first step into a larger world."

So happy you guys were nice with helping him. I'm finally making my switch to Android (in 3.5hrs). I can't wait to get home and root and figure it all out. Seems a TAD more difficult than it was with WinMo. There's SOOOOOO much info here, it's difficult to figure out WHERE start. But this thread helped at least figure out WHICH guide to follow initially.

recovery 3e modified to work like recovery 2e - Updated 01/23/2011

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.

ROM Manager Reboot?

Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.

Velshtein said:
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Click to expand...
Click to collapse
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.

diablo009 said:
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
Click to expand...
Click to collapse
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?

Velshtein said:
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Click to expand...
Click to collapse
Ok. I'll explain to the best of my knowledge.
The zip I gave u is the most non-intrusive way of CWM. No ROM manager installer is needed on phone apart from placing this zip on sdcard root.
When the phone boots up, it loads the default recovery console. When we select "reinstall packages", it loads "update.zip" on the sdcard root by default. Since the update.zip we have there is the CWM zip, it loads it therby loading CWM console.
If u don't want CWM, just delete this update.zip.
Hope this helps.

I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?

NISMOFO said:
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
Click to expand...
Click to collapse
Yes best to do so

All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.

MikeyMike01 said:
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
Click to expand...
Click to collapse
I got the ROM backup working. I guess I was too impatient the first time. I cleared/moved a lot of stuff off my internal SD card too....doubt that it mattered.
But it works quite well.

[Q] [CWM Manager][Help needed][Flash Stock firmware option]

CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
Click to expand...
Click to collapse
Is what im following. I have the RocketRom files extracted into the internal SD card /external_sd/firmware folder and one on the external SD card with the folder firmware. The rocketRom zip had META-INF - system - modem.bin - zImage. But when i click on Flash stock firmware it says it cant find anything. Did i do something wrong? Or actually im not sure what im doing wrong.
Thanks for any help!

Renren1403 said:
Is what im following. I have the RocketRom files extracted into the internal SD card /external_sd/firmware folder and one on the external SD card with the folder firmware. The rocketRom zip had META-INF - system - modem.bin - zImage. But when i click on Flash stock firmware it says it cant find anything. Did i do something wrong? Or actually im not sure what im doing wrong.
Thanks for any help!
Click to expand...
Click to collapse
Stock firmware is always .tar files, Rocket ROM is .zip file..
Put the whole Rocket ROM .zip folder in your sd card (do not unzip it), open Mobile Odin and choose flash update zip and then choose RocketRom.zip
EDIT: or you can just put the zip in your sd card, reboot into recovery, choose install zip from sd card and then reboot system

Thanks i tried that. But when it rebooted everything looked the same. Is that what the rocketrom looks like?

matius44 said:
Stock firmware is always .tar files, Rocket ROM is .zip file..
Put the whole Rocket ROM .zip folder in your sd card (do not unzip it), open Mobile Odin and choose flash update zip and then choose RocketRom.zip
EDIT: or you can just put the zip in your sd card, reboot into recovery, choose install zip from sd card and then reboot system
Click to expand...
Click to collapse
but if i use recovery wont it increase my counter?

Renren1403 said:
but if i use recovery wont it increase my counter?
Click to expand...
Click to collapse
No, recovery and mobile odin will not increase your flash counter
Flash counter will increase only if you flash custom firmware using PC Odin

Renren1403 said:
Thanks i tried that. But when it rebooted everything looked the same. Is that what the rocketrom looks like?
Click to expand...
Click to collapse
Rocket ROM is stock-like custom ROM so yes it will look the same
Go to Settings > about phone and check

Thank you so much for your help.. The official CF posts for flashing ROMs are so confusing and such. Thanks for clearing it out for me +1

matius44 said:
Rocket ROM is stock-like custom ROM so yes it will look the same
Go to Settings > about phone and check
Click to expand...
Click to collapse
I just did it via recovery mode, the animation starts then goes to a black screen. Is it rebuilding its cache?

Renren1403 said:
I just did it via recovery mode, the animation starts then goes to a black screen. Is it rebuilding its cache?
Click to expand...
Click to collapse
Did the flash went successfully?
Try to reboot couple of times, that might help..
If not, reboot to recovery, do cache and dalvik wipe..
If not, try to reboot into recovery and do factory reset/data wipe/cache/dalvik wipe and reboot..you will lose your data this way

matius44 said:
Did the flash went successfully?
Try to reboot couple of times, that might help..
If not, reboot to recovery, do cache and dalvik wipe..
If not, try to reboot into recovery and do factory reset/data wipe/cache/dalvik wipe and reboot..you will lose your data this way
Click to expand...
Click to collapse
It didnt say any errors when installing so it shouldve of went fine.
Im doing a cache wipe. and it just went to a black screen after "calling all speed demons"
Ill doo a factory wipe then and get back to you. Thanks for your help so far!

I re did the whole process this time. And it still goes black after "calling all speed demons". Should i wait during this time? In the s2 forums i read about it going like this because it is building cache or something along those lines.
I judt reread the whole RM thread. I didnt read the "flash 22 first" bit. Ill do that and hope it works that time ><!

How to Install 4.2 images, keep root and all data

**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!