Related
**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!
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
ImMrBS said:
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
Click to expand...
Click to collapse
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Danny201281 said:
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
ImMrBS said:
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
Click to expand...
Click to collapse
Yep that's about right. Running the script shouldn't do any harm but since you already experienced the Factory reset. The command should no longer be in your bcb anyway. As far as I'm aware this only happens once after a new flash and shouldn't repeat every time you use recovery.
But using the zip to clear your bcb is not a bad idea for piece of mind.
Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?
mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act
The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:
I have TWRP 2.8.7.0 and the latest VZW 5.1 debloated ROM from VitaTaf's thread. It's been a while since I backed up my /sdcard/ to computer. I realized that my TWRP backups are visible when booted into recovery; however, the /sdcard/TWRP/ folder is empty when booted into Android. Using Root Explorer, I am able to see the backup files in /data/media/0/TWRP, but the same files do not show up when connected to a Windows computer via MTP (which, if I'm correct, leads to /sdcard/).
I have tried the restorecon command from HERE, but the backups still do not show up in /sdcard/ after a reboot. I am able to move them to a different folder on /sdcard/, but it takes a long time and does not seem to be an actual solution. Trying to move the backups from /data/media/0/TWRP to /sdcard/TWRP/ results in an error.
Has anybody else encountered this strange issue? Any assistance would be appreciated.
AFAIK the folder is hidden. Try boot into TWRP, connect to the PC and then mount storage in TWRP.
A second option is directly backup to an external USB-Drive.
Thanks for the tip. I figured it might be an issue with permissions, and your suggestion gave me an idea. I booted into recovery, deleted the /sdcard/TWRP/ folder, rebooted into recovery, and created a backup in the newly created TWRP folder. It now shows up normally in Android and when connected to PC via MTP.
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
wittier said:
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
Click to expand...
Click to collapse
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
NLBeev said:
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
Click to expand...
Click to collapse
thanks. it is the latest TWRP.
I fixed it, see above, it wasn't the drivers on the PC.
The PC works with my other N6. This N6 has issues.
The workaround of wiping in TWRP fixed it. I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
wittier said:
... I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
Click to expand...
Click to collapse
Updating TWRP to the latest version is a good practice.
wittier said:
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
Click to expand...
Click to collapse
I updated my other N6 last night.
After flashing stock ROM and TWRP and booting to TWRP only, I didn't have to wipe before I could push files to the phone.
The other phone is more difficult.