Hello everyone! I'm new to this forum and kinda newb in this all business..
I have a rooted Nexus 1 device with recovery, I recently updated my phone to the following:
Build Number: FRF85B
Baseband V: 34.41.00.32H_5.08.00.04
After updating everything works fine except from the Market, which is gone!
I tried updating to CM6 with Google Addons and the Market worked, but I didn't want to lose all my applications, SMS, etc.. so I restored..
Is there anything similar to Google Addons but for Froyo 2.2?
You're just about 2 generations behind, and running non-official build (which disables paid Market). Why do you expect the Market to work?
Update to FRF91, or to recent FRG83.
Use the bold link in my signature to get to the collection of all official stock ROMs and OTAs, and update your FRF85B to FRF91 by applying an update from there.
As I mentioned I'm a noob.. :/
Anyway, I downloaded FRF91,
when I'm trying to flash it I get:
E:No signature (575 files)
E:Verification failed
Installation aborted.
Same thing with FRG83.. What went wrong?
What recovery are you using? Use Amon_RA's 1.8 or above, and disable signature verification.
And if you flash full ROM (~80 MB) - you'll lose the root and the recovery. Be prepared to root again and reinstall the recovery. Wiki can guide you with root.
Ok, I updated to Amon_RA 1.9.0-alpha (1.8 link was broken) and updated to FRF91.
Still... No market!
What am I gonna do?!
Check that you indeed have FRF91 on your system (Settings/About/Phone).
Then go to Settings/Applications/Manage/All/Market, and do "clear cache" and "clear data".
Then run Market.
Checked and I do have FRF91 installed..
And I can't do that because the market is not there... It vanished from my device..
BTW Jack, I really really appreciate you trying to help me, thanks a lot.
If you don't have Market at all - then you're missing its APK that you accidentally erased.
Since you have root (and if you don't - then root):
adb push Vending.apk /system/app/
Get the Vending.apk from the FRF91 ROM you've downloaded, it's under - surprise - /system/app
In case it doesn't help - then something is bad in your setup, and the best thing would be to wipe and reinstall everything from scratch, including the ROM.
Man I'm such a noob.. I can't manage to push it, i'll describe what i've done step by step, tell me what i've done wrong please..
1.Turned USB Debugging on.
2.While the device is turned on (not in bootloader) i connected it to my pc, I didn't mount the device.
3.In SDK tools folder i opened the command window.
4.I typed adb devices, my device was found.
5.I typed adb shell, a $ symbol appeared.
6.Typed adb push c:\sdk\vending.apk /system/app
(I placed the vending file in c:\sdk)
7.Got: adb: permission denied
Either you already have it on your phone, or you're not rooted.
do:
adb shell ls /system/app/V*
(Android is case sensitive!)
You should see "Vending.apk" present. If present - it'll be easier to wipe and reinstall than to try and solve the problem. If not present - check if you have root by running any root application.
Man.. It's present..
Guess I'll wipe and reinstall everything.. Hate to lose everything though (especially my unlimited Shazam lol)....
BTW, I need to also reinstall the radio?
Or just the ROM and the ROOT?
And should I do it in a certain order?
Install Titanium backup, back up the applications, wipe, install a custom ROM, restore Titanium backup.
You won't gonna believe, I was about to wipe it all and then I found this file - http://www.multiupload.com/HV1MWXXXY0 and managed to push it!
Market is working fine right now.
Thanks a lot for your help!
I learned a lot today thanks to you :]
Related
Hi alll,
I have a rooted (i think) HTC Legend. I have completed step 1 of the root but had errors with step 2. Now I want to install clockwork rom manager so I can install azure.
But when i download azure using the rom manager app (and after flashing clockwork) it asks me to press OK for a reboot but nothing happens. I have also checked the recovery that I have and it is the one installed as part of the root.
I have tried downgrading the recovery to an older clockwork version, which works and then I installed the latest clockwork again, but i still have the recovery from the step 1 root.
How do i get clockwork recovery installed?
You mentioned errors with step 2.
Did you stick a freshly formatted SD into phone instead of goldcard??
Sent from my Legend
did you downgrade before rooting?
Check your root.
Install a terminal emulator from the Market, if you don't already have one.
Fire it up, type su. If you don't get an error about permissions, then you should have root.
E.E.
chances are, if it did not reboot your system, your not rooted...
Hi all,
Seems if I am having nearly the same problem. The Clockwork Recovery is always freezing when I try to install. So I downloaded the Terminal Emulator from the Market, but when I try to run: "Applikation Terminal Emu (Process com.android.term) has been closed unexpected. Please try again."
SuperUser Permission Reuest also doesn't work, there is happening just nothing when I try to start. Btw thats the same headline what I am having when freezing while installing clockwork recovery.
What went wrong while rooting? Can someone help please
I had some Problems with step2 btw .. because my Legend is the only hardware to get access to the SD Card. So i restarted the phone between step1 and step2, used it as harddrive just to format the SD Card agaein. The I jumped back and started and finished step2 just fine (thats what I thought )
Sorry guys, I have searched through, tried all possible things... but cannot get things working... here's my story (long, but gives the whole picture)
1. Was on CM 6.0 (stable) and Amon RA 1.7 recovery
2. Got a new SD card (8gb class 6)
3. Had Nand backups, so just removed the old card and inserted the new
4. Booted into recovery, partitioned SD card, copied CM 6.1.0 RC and gapps onto the SDCard
5. Performed Wipe Data/Factory reset, Wipe cache, Wipe Dalvik-cache and flashed CM 6.1.0 rc and gapps
6. Booted into the ROM, signed into my account, got all my apps from market
7. Everything was running fine
8. Booted into recovery, made a Nand backup and installed Steel my Elegance
9. Booted into the ROM and realized something was not correct, so decided to restore from the Nand backup
10. Booted into recovery and tried to restore - failure, asked me to run nand backup from adb
11. Did that but that did not resolve the situation
12. Performed step #5 (above) again and got it to the original state
13. Did not login into my account, as I wanted to get a backup of a fresh install
14. Booted into recovery made a Nand backup successfully
15. Just to be on the safer side, tried restoring... did not work. Same error - run SH from adb - tried that, but did not work
16. Read somewhere on the forums to wipe cache before backup and try, did that backed up and tried restoring - no go
17. Decided to flash ClockWork recovery - did that through terminal (ROM booting properly)
18. Booted into recovery - successfull
19. Tried creating Nand backup - failed at Cache - cannot image cache error message or something
20. Performed format SD card, cache, system and all other formats available from the recovery (ClockWork mod)
21. Tried performing nand backup - created some folders/files under the clockwork mod folder with junk characters
22. Performed a SD card format from computer (FAT32)
23. Booted into recovery and tried nand backup - no go
24. Decided to revert back to Amon RA 1.7 - flashed through terminal and rebooted into recovery - phone won't go to recovery
25. Though there might be some problem with the img file, so downloaded from multiple locations and tried it - still no go
26. Followed all sorts of instructions - mount/remount, flash_image - no go. When I do flash_image recovery <image name>, the command exits without any errors, but still can't boot into recovery
27. Installed ROM manager and flashed clockworkmod recovery from within, still no go.
28. Performed "Fix permissions" - ended with "Could not run some privileged commands"
29. I can still boot into the ROM and when I go to terminal can do SU - takes me to "#" from "$" - so I am guessing I still have root
It just doesn't add up... and I feel very lost, right now. I guess the only thing remaining to do is go back to 2.1 RUU, reroot and go from there. Is there any other way? Or did I do something wrong?
Can someone please help?
Edit: I had enough battery juice or wall power plugged into the phone while trying the backups and restores...
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
go to impalers cyanogen mod q&a, ask there, impaler is really knowlegable and helpful, you should get some concrete help.
I don't think this has anything to do with CM, else would have posted there.
Thanks anyways.
cordell12 said:
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
Click to expand...
Click to collapse
Checked that, everything that needs access seems to have it.
Any other ideas? I am so close to going RUU route......
Maybe this can help? I dont know never had this happen?
http://forum.xda-developers.com/showthread.php?t=845069
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
andythegreenguy said:
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
Click to expand...
Click to collapse
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
cordell12 said:
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
Click to expand...
Click to collapse
No kidding... . It was so frustrating, just going through it all.
Originally, I had rooted my phone that had 2.31.651.7 on it. So, I applied that RUU and went through the root. It seemed to have rooted fine, but then it won't allow me to flash recovery - did the same steps as I had performed during my first rooting process, but didn't work. Then went through all possible ideas suggested on the forums... still no luck. So, finally put the 2.27.651.5 RUU, followed regaw_leinad's rooting method and everything worked out.
All-in-all a good learning experience .
BTW, for anyone that is reading, I think the issue was a corrupted SD card. I might have pulled it while the phone was running and then applied a corrupted recovery image.
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...
I will probably get screamed at by seasoned vets but....I cant find it anywhere.
I am not really the techy type but I am confident that I can root my device with the instructions posted by Regaw.
Once I root, I would like to goto the most stable upgrade to at least 2.2.....
I dont need any super flashy mods, something similar to stock that has all of the functionality would be great. But it needs to be dumbed down and step by step how to instructions. Please dont brick my phone.
Well once you are fully rooted download the rom you want (dec 31 is the latest on for his version i believe) make sure u also download the GAPP (gapps-mdpi-20101218-signed) put it in your sdcard somewhere so u can find it through recovery.
Turn off phone - take out battery to make sure its off, put it back - hold the VOL DOWN and HOME and then press the END button
wipe data and factory reset / mounts and storage / format boot / format system / press back button / click advanced / wipe dalvik cache / click back button / install zip from sdcard / find the ROM and install it / go back to sdcard again find the GAPP and install / click back / Reboot system
make sure u give thanks to jaybob thread is here http://forum.xda-developers.com/showthread.php?t=731659
his download file here - http://www.mediafire.com/JB_CM6_ROMS
OK So i lied.....I tried to to root with the Regaws one click and it would just sit there forever....BUT when I disconnect and quickly reconnect it looked like it was going through the rest of the motions and then it said rooted.....But I dont think I was actually rooted.
Tried the RUU to roll it back and was not successful until i read another persons post where it said to go into Hboot and run RUU from there...BINGO it worked, rolled back to stock.
Then tried the Regaw rooter again, and nothing.
So then I decided to go manual and downloaded and unzipped everything in the proper places, but I can only get to the --- adb devices command---i have tried to verify everything in the post to resolve the issue but to no avail ----uninstalled HTC drivers/sync--reinstalled from SD--uninstalled and then downloaded the newest version from the market---still nothing.
I am still months away from an upgrade and I am getting antsy for something new, so a rooted Hero with a 2.2 platform would be real nice right about now. I know I CAN do it if given the right tools and directions.
If someone can give me step by step directions in plain language that would be awesome.
Ebaum1 said:
If someone can give me step by step directions in plain language that would be awesome.
Click to expand...
Click to collapse
Email or gchat me at [email protected] and I'll walk you through it
Download Superoneclick and root that way. Easiest and fastest way. Once that is done download Terminal Emulator and busybox installer from the Market. In my signature go to the thread about CWM recovery images. Download the most recent one and unzip the file. Take the recovery.img and place it on your SD card. Now open busybox and install a version. Once that is done open up Terminal Emulator and enter these commands:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される。
Must give thanks to ajrty33, this dude was relentless it getting me rooted and ROMed to jaybobs latest.
One click root APK... super easy
http://forum.xda-developers.com/showthread.php?t=743289
For some that aren't too tech savvy this link helps with rooting and re-installing stock roms. . . unrevoked.com/rootwiki/doku.php/public/forever
**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!