Hey there!
I will explain how to install Cyanogenmod 9 OR 7(the FXP ones), found here: http://forum.xda-developers.com/showthread.php?t=1447542, and here: http://forum.xda-developers.com/showthread.php?t=1780322
You will need an unlocked bootloader, and the nessecary files to get into fastboot etc. This is not covered in my tutorial. You will have to find someone else's tutorial for that.
I made a step-by-step tutorial.
For CM10, you need a custom recovery beforehand.
If you want to install CM10, you need to flash the kernel last. (Do steps 4 - 7 after 12. Manually reboot in step 8, and instead of pressing reboot during step 12, power off and flash the kernel (step 4 - 7)
1. Make sure you have all the drivers installed, made a nandroid backup (only if you already have a custom kernel installed, if not, you can skip this) and have an usb cable, usb port (preferably no hub) and your phone near you.
2. Download the CM10/CM9/CM7 rom from their respective threads.
3. Open (don't extract!) it with WinRAR or your program of choice. Copy the boot.img to the folder your fastboot.exe is in (for me, this is C:\Program Files\Android\android-sdk\platform-tools). Then, put the zip file on your phones memory card.
3.5 (optional) Also download the Gapps (Google Play etc.) suited for your rom of choice and put the zip file on your memory card. I strongly advise you to install this.
4. Put your phone in fastboot mode (hold the search key while connecting it to your pc using the usb cable. The notification light should light up blue. When it's blue, you can release the search key.
4.5 Read steps 5-7 carefully. I have made a .bat file that will do this for you. If you choose to use it, place it in the same folder as your boot.img, and then launch. This won't work if you have renamed the boot.img. If you don't trust this, you can right-click it and hit edit. This way you'll see it says exactly the same as steps 6 and 7. Feel free to do it manually though. http://www.2shared.com/file/fPzWv4of/Flash_kernel.html
5. I assume you have Windows Vista or 7. If you do, shift-click on a empty place in your fastboot folder and click "open command prompt here" or something similar (my Windows version is Dutch, so I don't know what it's called in English).
6. Flash the kernel using this command: fastboot -i 0xfce flash boot boot.img. Note: it might be 0x0fce
7. Reboot the phone using this command: fastboot -i 0xfce reboot. Same for this one
8. While the phone is rebooting, spam the volume down key. You will now go into a recovery. Use the volume keys to navigate, and the home key to select (unless instructed otherwise on the recovery's thread). (You can now unplug the cable, but it can't hurt to keep it plugged in) If you haven't already, make a backup under "backup and restore".
9. Press wipe data/factory reset (this will of course wipe your data. Don't worry, we made a backup, remember? Note that restoring this backup will also restore your rom. Use Titanium Backup to back up your apps (requires root)). After that, also wipe your cache and Dalvik cache.
10. Select "install zip from sdcard", then "choose zip from sdcard". Navigate to the zip you put on the sdcard during step 3. It will now install the rom.
11. (optional) Also install the Gapps, same way as the rom itself.
12. After you finished installing, press reboot system now, and it will boot Cyanogenmod.
Congratulations, you just installed Cyanogenmod!
If I made any mistakes, please let me know.
I am not responsible for any bricked phones, broken GPU's, force-closes and killed pets.
If this helped you, I would appreciate a "thanks".
Good luck!
Ridder
(If you want others to be able to use this guide, leave a comment. This will bump it up =))
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Oh well, it works for me so.. I copy-paste it anyway.
savage24x said:
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Click to expand...
Click to collapse
You're right about the command correction, but I've been told that on some machines, that command is necessary to communicate with the phone correctly. So it's not that it's not necessary across the board, but it's not necessary for you. Nor is it necessary for me.
um can someone enlighten me why this is posted when there have been multiple other guides if you use the search button? sorry if i miss understood
Xperia4life said:
um can someone enlighten me why this is posted when there have been multiple other guides if you use the search button? sorry if i miss understood
Click to expand...
Click to collapse
Because the other guides are imo not very clear. Mine says exactly when to press/release buttons, how things work (CWM recovery) etc. That's why I made this.
0x0fce is the same as 0xfce in hex iirc
Sent from my Dark R800i using Tapatalk 2
Just an FYI, I linked to this thread, because it is the most comprehensive install guide for CM9,
Thanks!
paxChristos said:
Just an FYI, I linked to this thread, because it is the most comprehensive install guide for CM9,
Thanks!
Click to expand...
Click to collapse
Thank you, I really appreciate it.
You could add instead of booting the phone and then entering cwm just boot in cwm with fastboot and booting the rom. Guess it really doesn't matter now that almost all kernels have included recovery.
Thanks for the guide, ridder!
Regarding the flashing of the kernel, can a kernel (pax's modified boot.img in my case) be flashed using either Fastboot or FlashTool?
Solar.Plexus said:
Thanks for the guide, riddler!
Regarding the flashing of the kernel, can a kernel (pax's modified boot.img in my case) be flashed using either Fastboot or FlashTool?
Click to expand...
Click to collapse
Well, to be honest, I don't have any experience with FlashTool for kernels. Fastboot does what it needs for me.
Yeah, I'm just curious if Fastboot Mode is simply Fastboot inside of FlashTool.
Solar.Plexus said:
Yeah, I'm just curious if Fastboot Mode is simply Fastboot inside of FlashTool.
Click to expand...
Click to collapse
Pretty much. It pushes the kernel to a fastboot device the same way command prompt does.
captain67 said:
Pretty much. It pushes the kernel to a fastboot device the same way command prompt does.
Click to expand...
Click to collapse
Thanks for clearing that up!
I have to say that im very happy with my actual setup
A2SD Amarullz dont work for me on stock rom so i have decided to go to CM7
i have 4GB of Internal Memory and this is enough for me ... My CM7 look like stock and i have install PS Pocket/LiveWallpaper/Stock Games and Widgets + Timescape, i can say its like CM7 Hybrid
eh....
CM7.2 is more stable, anyway.
thanks so much for this b4 i was using this command for fastboot - fastboot flash boot boot.img
hey Ridder,
thank you for your guide it was very helpful for me, without it i don't know if was able to flash the cell phone of my wife. good work!
savage24x said:
I thought it was 0x0fce? -I 0x0fce is not necessary either.
Sent from my R800x using XDA
Click to expand...
Click to collapse
It's necessary for me! Needed for some PCs. Usually AMD based PCs are affected by this.
Related
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
This comes with the .img of Amon_ra, 3 batch files to reboot into bootloader, flash it, then reboot into recovery (will need to type reboot recovery) into the shell for the 3rd batch file (it tells you so) then you are immediately into recovery. I made this batch file and if you repost, please give proper credits. This script can be easily modified to flash any recovery for any phone since it's just generic commands. This currently is using amon_ra for the HTC Evo 4g and can be used after gaining s-off using Revolutionary or any other root method. I used the install recovery.bat for switching quickly from Twrp to wipe for my roms. Anyway, here is the bat. Instructions are included when you run each batch file. So just extract these to your desktop as is meaning don't put the .bat files in the same folder as all the other files. They need to be seperate.
You run them in this order: Reboot1.bat>Recovery install.bat>Reboot2.bat
^ in order from left to right.
http://dl.dropbox.com/u/15069134/Recovery flash.zip
Thank you
Sent From DEEZ
popper668 said:
Thank you
Sent From DEEZ
Click to expand...
Click to collapse
Happy to help.
Sent by breaking the sound barrier
Hey all...I'm sorry for sounding like such a noob (trust me i'm not as big as one as you may think) I'm just having a hard time grasping the idea of updating my Nexus. Let me explain:
I'm currently running stock rom but have Matr1x kernel on my phone. The only thing I've changed so far are a few icons (by pulling files from the nexus toolkit, replacing the icons and pushing them back to my phone).
I would prefer not to have to go through and redo all my icons, and would just like to get 4.2 onto my phone.
I looked over the directions on how to do this, but for the life of me (and IDK why) i can't seem to get my head around it...and it's making me feel real real stupid...
can someone please explain to me like i'm 5 how to do this? Or maybe just point me in the direction of a youtube video that will walk me through it...?
Thanks in advance and sorry for being such a noob...
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
estallings15 said:
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
Click to expand...
Click to collapse
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
zbt1985 said:
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
Click to expand...
Click to collapse
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
estallings15 said:
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
Click to expand...
Click to collapse
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
zbt1985 said:
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
Click to expand...
Click to collapse
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
estallings15 said:
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
Click to expand...
Click to collapse
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
zbt1985 said:
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
Click to expand...
Click to collapse
There should be a fastboot.exe and a few .dll files, as I recall.
Could someone upload all the latest files needed for adb and fastboot in a zip for him? Won't take you 5 minutes. I'm not by my computer.
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
dEris said:
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
Click to expand...
Click to collapse
I wanted stock...i only want this for 1) getting updates faster than cm 2) being able to update the hard way and not be a kiddy about it...
Better for me to learn...
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
just follow efran's guide, he got the step by step: http://forum.xda-developers.com/showthread.php?t=2010312
gravitysandwich said:
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's what is confusing me...
Sent from my Nexus 4 using xda app-developers app
Download this http://d-h.st/iy0. Unzip it. Plug your phone I'm the computer, go to the directory where you installed the toolkit. (Right click on the shortcut/properties it should say it there) go in the directory, FLASH ITEMS HERE folder. Put the boot.img and system.img in there. (Radio.img is optional). Open the toolkit and go to flash images. Flash boot.img first. The directions should be on the toolkit. Then system and etc... Make sure you put it in fast boot or type no when the toolkit asks if your in fastboot mode. This will NOT delete your data. When you flashed everything, go to settings on your phone. (If there is a bug with updating it through settings, clear cache and data for Google services framework and force stop it. Then go to cache on root explorer (/cache) and delete the corrupt/partial update and try Again). Once you reboot, cwm will ask if you want to install update. Hit yes and install untrusted package. Then it will try to replace cwm with stock recovery so hit no. If you lost your root then get supersu from the play store and install the binaries via cwm.
Hope this helps.
Sent from my Nexus 4 using xda premium
---------- Post added at 12:11 AM ---------- Previous post was at 12:02 AM ----------
Btw I chose to flash it through toolkit because I was afraid you would've got the commands mixed up and you would never get it. One day you probably will
Sent from my Nexus 4 using xda premium
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
zbt1985 said:
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can thank you your phone.
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
gravitysandwich said:
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Haven't had a chance to try it, doing it now...thanks!
After few hours of playing with the new Android 5.0 Lollipop on my Nexus 7 2013, it looks like a stable OS with dramatically improved performance and battery life.
So I decided to write a simple guide to teach you how to flash it on your flo, and successfully get root access
This tutorial works on Windows.
This process erases everything from your nexus, so BACK UP!!!
-------------------
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
-------------------
1. Unlocking Bootloader
So the first step is to unlock your bootloader, but I think you already done that. If you don't, there are lots of tutorials on Google. (Your nexus doesn't need to be running original rom, or anything stock, if you can get to bootloader normaly, you're fine.)
-------------------
2. Flashing the 5.0
We need to flash Android 5.0 Developer preview! (obviously).
1. Go to
Code:
http://developer.android.com/preview/index.html
and download the .tgz for Nexus 7 (Yes, your device IS called razor... )
2. Unpack it with Total Commander or something, I don't care..
3. Install standard ADB and Fastboot from this link:
Code:
http://forum.xda-developers.com/showthread.php?t=2588979
4. Use WugFresh to install ADB and Fastboot drivers (If you haven't done that already)
5. Restart your PC!
6. Enable USB Debugging.
7. We need to test, if your drivers are working correctly so open up command prompt and,
Code:
adb reboot bootloader
Wait until it reboots to Bootloader and then
Code:
fastboot reboot
If it rebooted back to normal state, we're ready to go!!!
8. Reboot to bootloader by:
Code:
adb reboot bootloader
9. Execute a flash_all.bat from the directory you extracted tgz to! (It needs to be extracted!!!) This process also reflashes your bootloader to newer version, and you already know that if it fails, you have a pretty nice paperweight, so DO NOT DISCONNECT YOUR DEVICE!!!
10. After everything is done, the Nexus will reboot and you have a working Android 5.0 on your nexus! Pretty cool already, but we are geeks and no android device is complete without the godly power of root access! So let's get into it!
-------------------
3. Flashing custom recovery, rooting, and fixing root!
1. Get your copy of the latest TWRP from here (I use 2.8.0.1):
Code:
http://techerrata.com/browse/twrp2/flo
2. Rename it to recovery.img and copy it to desktop
3. On desktop, press shift + right click on blank spot. (If you don't have one, move it somewhere else where you can find it) Select Open command window here.
4. Enable USB debugging on your nexus again.
5. Move this zip to the root of Nexus's internal memory.
Code:
http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
6. Reboot to fastboot
7. Format cache by:
Code:
fastboot format cache
8. Flash the recovery! (make sure you're in the directory as the recovery img.. you can check that by typing dir.):
Code:
fastboot flash recovery recovery.img
9. On your nexus, choose to reboot to recovery (volume buttons up down, power to select.)
10. In TWRP install SuperSU zip.
11. Reboot your system.
12. After it booted back to Android, and you see the SuperSU in apps, reboot again
14. If you already tried, your root isn't working, so we need to fix it by flashing the chainfire's custom kernel. We 'll do it the fastboot way.
15. Reboot to Bootloader
16. Download the custom kernel from:
Code:
http://forum.xda-developers.com/showpost.php?p=56109923&postcount=6924
17. Extract it, and flash it the similar way as recovery, but with using this command. Again, check if you're in the same directory as the boot.img!
Code:
fastboot flash boot boot.img
18. Now, just reboot with:
Code:
fastboot reboot
19. DONE!
Your Nexus 7 have working Android L with root access. Coolness overload!
Let me know if it worked for you!
If yes, please press that thanks button
Awesome! One question, do I have to unzip the image-razor-lpx13d.zip file inside the tgz file as well?
andy_rose said:
Awesome! One question, do I have to unzip the image-razor-lpx13d.zip file inside the tgz file as well?
Click to expand...
Click to collapse
No
I read the 5 bootloader works for KK. IF I'm ok with the risk and I've completely backed up the disk, can we switch back to kk or is this a one way trip? If I restore the twrp files, can we treat 5 like any other ROM?
Root dont work for me on my nexus 7 2013 flo ( i use ur tutorial,but i still have no root
How many guides do we need? Lol jk
Have you flashed the custom kernel? Try installing the SuperSU again. What version of SuperSU are you using?
jimbob_sf said:
I read the 5 bootloader works for KK. IF I'm ok with the risk and I've completely backed up the disk, can we switch back to kk or is this a one way trip? If I restore the twrp files, can we treat 5 like any other ROM?
Click to expand...
Click to collapse
I will try this for you, give me an hour.
Sent from my Nexus 7 using XDA Free mobile app
Yup, I flashed CleanRom (4.4.4) from recovery, and it's working just fine! And BTW, yes, you can restore to android 5.0 from recovery just fine
Sent from my Nexus 7 using XDA Free mobile app
I did the exact same thing last night when chainfire's post on g+ appeared.
so I do have root (2.14)...I guess, because Adaway works, and TiBu says I'm rooted as well. On ES File Explorer, I cannot access /system and in Titanium I cannot delete apps (Couldn't find APK). I tried the last version from store, and the test build from July/August, when L preview popped up for the first time.
Any advice?
horst0815 said:
Any advice?
Click to expand...
Click to collapse
It looks like we just need to wait for final version of Android L. After that, maybe more hackers will be interested in getting the root 100% done.
Sent from my XT1032 using XDA Free mobile app
https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
Sent from my Nexus 4 using Tapatalk
Hmmm, I use proxydroid because I am sitting behind a http proxy with authentication but an android 5 the settings have no effect. Does someone getting this to work?
Is there any flashable fully working zip till for this final preview?
AnkeshReborn said:
Is there any flashable fully working zip till for this final preview?
Click to expand...
Click to collapse
Nope you 'll also need the new bootloader.
Sent from my XT1032 using XDA Free mobile app
AnkeshReborn said:
Is there any flashable fully working zip till for this final preview?
Click to expand...
Click to collapse
Yes its there in Android development section.
Sent from my SM-G900W8 using Tapatalk
can i get some quick opinions, I just unlocked my device and am about to root it, should I flash stock 4..4.4 then root or just root on 5.0, I ask because i'm wondering if i'll have more trouble flashing the final or updating to the final release with root
I guess what i'm asking is, which way is gonna be the least pain in the rear when rooted. ;P
brar.arsh said:
Yes its there in Android development section.
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
It have bluettoth issues but then recently released zip by multi ROM dev tadassar,I haven't tested can any of you can?
https://s.basketbuild.com/devs/Tassadar/stock_zips/
Sorry for bad English.
Flashed the kernel and now have root. Thank you!
Scipizoa said:
can i get some quick opinions, I just unlocked my device and am about to root it, should I flash stock 4..4.4 then root or just root on 5.0, I ask because i'm wondering if i'll have more trouble flashing the final or updating to the final release with root
I guess what i'm asking is, which way is gonna be the least pain in the rear when rooted. ;P
Click to expand...
Click to collapse
From what I've read, you'll need a clean flash to final 5, so it makes little difference. I'd flash whichever you want to use until final 5 is out and fully rooted.
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
@levone1 link isn't working! pls fix.
itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.
http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).
levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?
NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.
NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM
This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.
No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.
aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.
Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728
levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.