Related
I was trying to install the Cyanogenmod M2 release on my Nexus 4 phone but I seem to have gotten stuck. The LG Nexus 4 phone is a very finicky phone when it comes to installing custom ROM's. My computer has 64-bit Windows 8 Professional installed. Here's what happened:
1. At a command prompt typed "adb reboot bootloader".
2. Once at the bootloader menu typed "fastboot oem unlock". Got the warning screen, selected Yes.
3. At the command prompt typed "fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img".
4. Immediately after the flash completed successfully selected Recovery from the bootloader menu. Got the Clockworkmod Recovery menu.
5. Selected the option to reboot in the Clockworkmod Recovery menu. Realized I made a stupid mistake and forgot to copy the Cyanogenmod ZIP file to my phone's internal storage space. My phone is now stuck at Google's colorful animated X for 10 minutes and counting.
What is causing this? Following these steps in this exact order did not cause this problem on the Sprint Nexus S I had before switching to AT&T.
You can push files (like CM10 rom and Gapps) with adb from the pc to the phone`s sdcard, look here for how to http://forum.xda-developers.com/showthread.php?t=1667929. Then flash in recovery. Good luck.
Thank, but I have to ask though. Is the command "fastboot oem unlock" wiping the ROM itself from the phone? The act of flashing a custom recovery immediately after this command shouldn't prevent the stock Android ROM that was already on the phone from booting.
techguy378 said:
Thank, but I have to ask though. Is the command "fastboot oem unlock" wiping the ROM itself from the phone? The act of flashing a custom recovery immediately after this command shouldn't prevent the stock Android ROM that was already on the phone from booting.
Click to expand...
Click to collapse
Yes it should have wiped the phone. Sometimes you'll have to clear cache manually in recovery as well.
Sent from my Nexus 7 using xda premium
techguy378 said:
Thank, but I have to ask though. Is the command "fastboot oem unlock" wiping the ROM itself from the phone? The act of flashing a custom recovery immediately after this command shouldn't prevent the stock Android ROM that was already on the phone from booting.
Click to expand...
Click to collapse
boot into recovery and clear your caches
ScumDroid said:
boot into recovery and clear your caches
Click to expand...
Click to collapse
This right here. Boot into fast boot flash a recovery and clear caches. It had mainly work for me by clearing /data which is found under mount / something something.
Did this last night when I loaded stock images.
Sent from my Nexus 4 using xda app-developers app
This is in no way the only way to go about getting your Nexus 7 back to stock. In my opinion however, it is the most tried and true and reliable method of getting it done. This is the way I like to do things and I know there are others that feel the same. This guide is for those people. If you would rather use the flash-all.bin script then be my guest. There are also toolkits that will get the job done. I hope this can help some of you.
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 at here.
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold the volume down key and the power button simultaneously. After holding both buttons for a couple of seconds, your bootloader should launch.
4) Type
Code:
fastboot flash bootloader bootloader-flo-flo-03.14.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-razor-jss15j.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.3 and ready to send in your tablet for warranty purposes if you so desire.
There already has a post that can do this
http://forum.xda-developers.com/showthread.php?t=2381582
:good:
miou said:
There already has a post that can do this
http://forum.xda-developers.com/showthread.php?t=2381582
:good:
Click to expand...
Click to collapse
This is a different way of doing things. This is the way that Google themselves provide to get your tablet back to stock. This is the way I prefer to do things as I like to be responsible for the code that is entered in my tablet. Maybe I'm just the weird one here and I am not saying they are wrong, just not a fan of the toolkits.
The only difference between this and flash-all.bat in the Google-provided factory restore is the optional fastboot oem lock
Not sure about your system, but (unless fastboot -w come back with error) on successful
fastboot -w update image-razor-jss15j.zip
My tablet reboots automatically, so the subsequent
fastboot oem lock
fastboot reboot
won't be run while the tablet is in fastboot mode.
In step three it says to press both volume keys and power to get into the bootloader but on our Nexus 7 I thought it was only volume down and power to get into the boot loader.
sfhub said:
The only difference between this and flash-all.bat in the Google-provided factory restore is the optional fastboot oem lock
Not sure about your system, but (unless fastboot -w come back with error) on successful
fastboot -w update image-razor-jss15j.zip
My tablet reboots automatically, so the subsequent
fastboot oem lock
fastboot reboot
won't be run while the tablet is in fastboot mode.
Click to expand...
Click to collapse
Just reboot back into the bootloader and lock it then
Sent from my Nexus 7 using Tapatalk 4
di3cbl said:
Just reboot back into the bootloader and lock it then
Click to expand...
Click to collapse
Yes, I understand what to do if I want to lock the bootloader.
What I was pointing out is the only difference between the instructions provided and what the flash-all.bat script (included by google in the factory image restore) does already is the "optional" step of locking the bootloader.
So the only difference actually doesn't work using the instructions here, you have to reboot the bootloader, which is exactly the same you would have done if you ran the flash-all.bat script and wanted to lock.
So this whole post could have been written:
1) adb reboot bootloader
2) run flash-all.bat script
3) optional - relock bootloader
adb reboot bootloader
fastboot oem lock
fastboot reboot​
geckocavemen said:
In step three it says to press both volume keys and power to get into the bootloader but on our Nexus 7 I thought it was only volume down and power to get into the boot loader.
Click to expand...
Click to collapse
You are correct. About to correct this in the OP.
sfhub said:
Yes, I understand what to do if I want to lock the bootloader.
What I was pointing out is the only difference between the instructions provided and what the flash-all.bat script (included by google in the factory image restore) does already is the "optional" step of locking the bootloader.
So the only difference actually doesn't work using the instructions here, you have to reboot the bootloader, which is exactly the same you would have done if you ran the flash-all.bat script and wanted to lock.
So this whole post could have been written:
1) adb reboot bootloader
2) run flash-all.bat script
3) optional - relock bootloader
adb reboot bootloader
fastboot oem lock
fastboot reboot​
Click to expand...
Click to collapse
I have had trouble in the past with the flash-all.bat script. My Nexus S never would work right with it and so ever since, I have always used the manual entry of the code. Takes 20 seconds to run all of it. Not too inconvenient for something I know will work.
ot: what should i tell the store when i go back to 'exchange' the tablet, once i do OP's procedure, will the store test it out and find no faults to exchange it?
tell them, wifi keeps dropping?
random reboots
can't update apps via googleplay store?
The second one is the hardest to reproduce, and they're not going to stand around and wait for it....
Does this guide still apply to the latest Android 6.0 Factory image?
^Yes.
The bootloader name as well as the image is obviously different so change that. The bootloader didn't change since at least 5.1 (04.05) so if you're running that you don't need to flash it the md5's are the same.
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.
Just wondering if anybody's tried to flash tn7 ROMs on their s7e? And does the s7e read the same model number as the tegra note? P1640?
Sent from my SGH-I317 using xda app-developers app
I've been stuck trying to figure out how to adb on my slate 7 extreme for weeks. Tried every driver and every cord and port. So while I'd love to confirm that it is the same... I'm still not sure.
Same here looking for a root
Sent from my HP Slate7 Extreme using xda app-developers app
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?
skysoblue said:
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?
Click to expand...
Click to collapse
It will work fine for up to about 10 minutes, then the screen will freeze and the only way to get it back is to hold the power down for 10 seconds and reboot it.
I am back on 4.2.2 right now, but when I have some extra time I might try a few things.
Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
Is it possible to just have root set up on 4.2.2? Would like to keep all partitions stock if possible (as well as the bootloader). Would this help with stability issues? Sorry if these are noobish questions but thanks in advance
Dude you gotta give us a detailed guide on rooting puuuhleeaase
nejinikko said:
Dude you gotta give us a detailed guide on rooting puuuhleeaase
Click to expand...
Click to collapse
+1
I tried a chinese program without luck. I just bought a keyboard which works with the wrong layout in 4.2 and works perfect with 4.4 which I have on my other devices..therefore I am really looking forward flashing it!
Almost plain tegra
Hi, I agree with @Mobilla I installed android 4.4.2 from this link but be extreme careful, backup your rom first, KitKat works fine but randomly android freeze all system, I tested ClockWorkMod recovery and work flashing root file SuperSU-v1.94.zip but I don't test backup from recovery, well maybe someone can help us to know why kitkat freeze chinese root method is complicated I rooted with this method I don't read chinese I click some buttons and it works. Sorry with my English, I'm from El Salvador, I speak Spanish
I couldn't run 4.4 more than about 10 minutes before locking up, so I went back to 4.2.2 (rooted).
You can download the stock 4.2.2 update.zip from HP's website if you experience the same issues
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
The rooting method is the same as for the TN7 with the exception of fastboot commands you need to specify the vendorid (e.g. fastboot -i 0x03F0 oem unlock) I didn't try the Chinese tool.
You can flash root from recovery once it is unlocked.
I tried looking for what was causing the lockup but I couldn't find anything in the logs. If anyone has any tips for hunting down the problem I would be happy to try.
CWM
Hi, I tested CWM from this link and it works with nandroids backup, but the default storage is strange: /storage/emulated/sdcard0 but in this dir I can't move or delete that backup and use storage space I use a root explorer and can't move or delete, CWM works to root the device with SuperSU-v1.94.zip :good: but not for backup, see ya!
Rooting Slate 7 Extreme
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download http://forum.xda-developers.com/showthread.php?t=2627654
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse
sparkly81 said:
Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
Click to expand...
Click to collapse
Thanks! Edited that in and fixed the link to the super tool. Hopefully this is clear enough to newer users such as myself Hopefully HP starts releasing stable updates for us but if not, things aren't too bad with root :good:
What can I do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.
What can i do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.
duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse
Succesfully rooted my HP Slate 7 Extreme 4409ra Tablet ty!
I have a Slate 7 Extreme 4400ca, and today installed the update listed on the HP webpage:
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6617231#N147
after a non-destructive installation, 'about tablet' reports that I'm running ANdroid 4.3, kernel 3.4.57-gc102837
Not 4.4 yet, but this should be helpful.
I haven't tried rooting yet.
Just a update on a simple way to root stock 4.2.2 slate 7 extreme
http://towelroot.com
Download apk
Install
Restart
Enjoy
Worked for me.
Hi.
First I have to apologize for being a noob, and if I am posting questions that has already been answered. I can't post these question in the original thread about F2FS file system, so I am posting this here.
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil
Hi!
Liloolil said:
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Click to expand...
Click to collapse
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
Liloolil said:
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil
Click to expand...
Click to collapse
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!
michael_ch said:
Hi!
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!
Click to expand...
Click to collapse
Thank you! I have now successfully rooted and installed CM11 on my Nexus 7.